Re: [translations] updating an up-to-date file?!?

[Francisco Vila <paconet.org@xxxxxxxxx>]

2010/11/24 Federico Bruni <fedelogy@xxxxxxxxx>:
> I have a silly question for you.
>
> This is the list of files I have to update:
>
> fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> check-translation | grep 'diff --git'
> diff --git a/Documentation/learning/common-notation.itely
> b/Documentation/learning/common-notation.itely
> diff --git a/Documentation/user/fundamental.itely
> b/Documentation/learning/fundamental.itely
> diff --git a/Documentation/user/preface.itely
> b/Documentation/learning/preface.itely
> diff --git a/Documentation/learning/tutorial.itely
> b/Documentation/learning/tutorial.itely
> diff --git a/Documentation/user/tutorial.itely
> b/Documentation/user/tutorial.itely
> diff --git a/Documentation/macros.itexi b/Documentation/macros.itexi
> diff --git a/Documentation/user/macros.itexi
> b/Documentation/user/macros.itexi
>
> (BTW, user/ is an old directory?)

This surprises me: Documentation/user/ does not exist in git.

cd Documentation
git ls-files | grep user

> So git thinks that it/learning/preface.itely must be updated but he's
> wrong (I checked the history).

It looks up to date.

> How can I tell git that the translation is up-to-date? should I put the
> new committish and include the file in the next patch? That's it?

Yes, just rewrite the committish in your file with the first one in
the output from

  git log Documentation/learning/preface.itely

after checking again that the accumulated recent history of the
original matches the current status of your file.  This is tricky but
as time goes by, your eyes will get used to detect such things.

Issue your 'make check-translation' command just after editing the
committish in the file and you'll see how it dissapears from the
output.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com