Re: Moving documentation to git

On 17.06.2017 at 10:22, Andreas Heigl wrote: > Am 17.06.17 um 08:04 schrieb Maciej Sobaczewski: > >> 3) When migrating from SVN $Revision$ to any solution, do not let >> outdated files on the translations to lost their status. If file a.xml >> in Foo translation is pointing to some other version of the English >> tree, please keep it this information - just in the new format. It >> happened once or twice in the past that such files were just marked >> as EN-Revision: n/a and for many translations it's still a problem >> to these days. Remember it's a difference of updating file a few >> revisions ahead vs retranslating it from scratch. I'm not sure if >> this point is understandable, so let me know if I need to elaborate. > > As I'm using git-svn for the transition that information "should" be > kept as it was before The thing though is that the revision-information > might actually be lost, but the last commit-date of the file is still > available so a connection via the last-commit date makes even more sense > to me. I'm afraid that last-commit date would not be sufficient. Consider somebody commits a quick typo fix (for instance, via a patch submitted to PhDOE) to an otherwise outdated translation; in this case the translation should not claim to be up-to-date. And yes, it would of course be better to update the translation right away, but unfortunately that is often not possible for time reasons. -- Christoph M. Becker