| Re: [translations] updating an up-to-date file?!? |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Federico Bruni <fedelogy@xxxxxxxxx>
- Subject: Re: [translations] updating an up-to-date file?!?
- From: Francisco Vila <paconet.org@xxxxxxxxx>
- Date: Fri, 26 Nov 2010 08:26:16 +0100
- Cc: Translations list at lilynet <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=HVfihhpE/RYzFq9yMHB7LhMLn4q1gAqinAxQ5bWWSI0=; b=bmPGLvqe7pDYucb6JMH0gSy1apUcDWyTHoz9zZxWX0LsFycObpSayJ7gLA/G+5Kwfm rMzeJcdldR+iZNzDvCYjsaVOAwgOYg18cC0IdS44wBzhi2roVABOzDdcj+jZGzQH+Mm4 Pwe/Sm6tbktD1so7yT22INTmKQ6ourEhPQpTg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JzVxlMeE5N9u2EFkQafzws0WlEY2YaGO9R3snr5Bcfh0GRuBG8MjTIQE2lb2DbS3M0 fGqjzdS2drJs4a9jOh5KpTIJgP8UMQFOuoC+RxRUop3PkFBwTOm0cvpH8noft76al3yT V2EObGCJjgSqeRehF5mzobNeKZRcPA41VwuNo=
2010/11/25 Federico Bruni <fedelogy@xxxxxxxxx>:
> Il giorno gio, 25/11/2010 alle 10.39 +0100, Francisco Vila ha scritto:
>> > I thaught I should always use the committish provided by this
>> command:
>> >
>> > git rev-list HEAD |head -1
>> >
>> >
>> > Why should I use the last committish of the original in this case?
>>
>> If the file is really up to date, both are equivalent. I use the
>> committish of the original as extra data for my convenience: that way
>> I know what exact version of the file am I in sync with.
>>
>
> It seems wise :)
>
> Last question about update. Actually, I prefer using terminal rather
> than web interface.
> Could you please tell me if the following procedure is OK?
>
> 1) I check the commit date of my last revision with 'git log
> path/to/file'
> This date doesn't tell me exactly which version of original file I used,
> but it's a good reference.
> That's why your "committish strategy" explained above seems much
> convenient.
>
>
> 2) 'git log path/to/original' and I pick the committish which is likely
> to be the one I used in my last revision. After checking and comparing
> I *should* be sure about it.
>
>
> 3) 'git diff committish path/to/original'
>
>
> This should give me the diff from that committish to current one.
>
> It's OK?
I have never done it that way because I think that's exactly what
check-translation does. Do you use it, and how? I redirect its
(usually very long) output to a file, then less -R thatFile. In
another terminal I can issue the edit commands.
Anyway, I'll take a more close look to your procedure.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com