On 2008/09/29 19:39 +0200, Francisco Vila wrote:
> Let's start from the beginning then.
>
> I obtain 'bad object' errors you don't. This makes translation status
> give wrong results for other languages than Spanish. What could I do?
Always complain to the list as soon as you encounter those "bas
2008/9/29 John Mandereau <[EMAIL PROTECTED]>:
> On 2008/09/26 à 12:53 +0200, Francisco Vila wrote:
>> For example, which branch is this object in?
>>
>> warning: fr/user/specialist.itely: fatal: bad object
>> 6bcad9cdc487270910758b1ee39cf3c8aee1015e
>
> Oops, it must be a committish I lost in a reb
On 2008/09/26 à 12:53 +0200, Francisco Vila wrote:
> For example, which branch is this object in?
>
> warning: fr/user/specialist.itely: fatal: bad object
> 6bcad9cdc487270910758b1ee39cf3c8aee1015e
Oops, it must be a committish I lost in a rebase. Fortunately I had not
used "git-gc --prune" just
2008/9/24 John Mandereau <[EMAIL PROTECTED]>:
> 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 overwritte
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
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.
Before git-adding and commiting these results, diff shows lines such as
@@ -214,7 +214,7 @@ translations.template.html.in; DO NOT EDIT !-->
Je
