lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot push translation status


From: Francisco Vila
Subject: Re: Cannot push translation status
Date: Fri, 26 Sep 2008 12:53:51 +0200

2008/9/24 John Mandereau <address@hidden>:
> On 2008/09/23 16:36 +0200, Francisco Vila wrote:
>> John,
>> I try to update the status reports as result of make
>> translation-status, but I'm afraid of erase valuable data from
>> languages other than Spanish.
>
> No problem, as I'd have overwritten bad status data with correct ones at
> next translation-status call anyway.
>
>
>> Before git-adding and commiting these results, diff shows lines such as
>>
>> @@ -214,7 +214,7 @@ translations.template.html.in; DO NOT EDIT !-->
>>     Jean-Charles Malahieude</td>
>>    <td></td>
>>    <td><span style="background-color: #1fff1f">oui</span></td>
>> -  <td><span style="background-color: #47ff24">partiellement</span></td>
>> +  <td><span style="background-color: #d587ff">N/A</span></td>
>>    <td>pré-GDP</td>
>>   </tr>
>>   <tr align="left">
>>
>> This tells me that you have proper objects for French, which I see as
>> bad objects on my side for these very same files, how could this be
>> corrected? thanks.
>
> I don't have this error, and all of my master and lilypond/translation
> branches has been pushed to git.sv.gnu.org.  If you want to be sure you
> have all committishes on git.sv.gnu.org, the least to do is fetching all
> branches; in this case, master and lilypond/translation should be enough
> (you will probably want to add stable/2.12 when it's created).

For example, which branch is this object in?

warning: fr/user/specialist.itely: fatal: bad object
6bcad9cdc487270910758b1ee39cf3c8aee1015e

Despite of what you said, I think that it doesn't worth that I push my
status with wrong data for other languages, even if you are to
overwrite them later. But if I manage to make status w/o errors, I can
push it easily.
-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org




reply via email to

[Prev in Thread] Current Thread [Next in Thread]