2009/5/27 Carl D. Sorensen <c_soren...@byu.edu>: > a) The changes to Documentation/de/* that move Lilypond -> LilyPond are OK > to commit, even though the commitish in the header of this file won't be > updated.
In particular, updating the committish for a file that is not up to date, would mark it as updated. Bad for the translator, who would lost the notice of pending changes from the originals. Otherwise, if you are sure that a file is bleedingly up to date, updating its committish would save work to the translator, because he does not have to worry for the file as it would not appear in our list of pendant work (only to realize that there is no work to do) -- Francisco Vila. Badajoz (Spain) www.paconet.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
