Bug#845297: Migration to Salsa

Laura Arjona Reina <[email protected]>
Newsgroups gmane.linux.debian.devel.www
Message-ID <77b4ed3d-9301-efb6-2978-bef33597bfbf__27124.432512983$1525018756$gmane$org@debian.org>
Hello again

El 29/04/18 a las 15:01, Paul Wise escribió:
> On Sun, 2018-04-29 at 13:49 +0200, Alex Muntada wrote:
>
>> Therefore, it seems that we'll need to translate CVS revisions to
>> commit IDs at least once after the repository has been migrated
>> finally to git and before any translation is performed.
> Please note that smart_change.pl needs to work with the new workflow.
> This means that we can't use git commit IDs in translations headers,
> unless we want smart_change.pl to make two commits instead of one.
I'm not an expert but getting smart_change.pl doing 2 commits looks like
easy to understand (and maybe to implement?).
First commit for the english folder, and then other commit updating
translations.
> The alternative is to use git file+metadata hashes, which can be
> calculated before a commit happens, placed into translations headers
> and used to diff between two versions of a file. I'm not sure how well
> this will fit with the existing webwml VCS modules though.
>
No idea, either :/

Cheers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.