Bug#845297: Website transition from CVS to Git - script including cvs-revisions in commits
On Sat, Dec 23, 2017 at 3:48 AM, Laura Arjona Reina wrote:
> I feel that "CVS version numbers" may match to some other present commit
> messages when parsing logs. Maybe it's useful to add some character(s)
> to make that line "unique"?
I have checked `git log` in my git-cvs webwml checkout and the phrase
"CVS version numbers" does not appear at all. The phrase "CVS version
number" (without the "s") appears twice.
>> After the repo has been converted, use the cvs-revisions file to add a
>> git commit automatically rewriting all the translation-check headers
>> to the git-based system Laura proposed.
> Somebody has to write a script... I don't feel myself skilled to write
> from scratch, but I'll try to read, understand and test if anybody comes
> with a proposal.
Anyone who is willing to work on this should note that there can be
multiple levels of translation-check headers chaining through
different files, for example:
#use wml::debian::translation-check translation="1.14" original="slovak"
#use wml::debian::translation-check translation="1.14" maintainer="David Prévot"
> Also, help on migrating the corresponding Perl scripts to handle
> translations with git instead of CVS is welcome! See the current status:
In addition, we need to fix a few scripts that directly use
Local::Cvsinfo to switch to using VCS instead.
$ git grep Local::Cvs | grep -v Perl/Local
french/international/french/desc.wml:my $cvs = Local::Cvsinfo->new();
smart_change.pl: my $cvs = Local::Cvsinfo->new();
stattrans.pl:my $cvs = Local::Cvsinfo->new();
stattrans.pl:my $altcvs = Local::Cvsinfo->new();
touch_translations.pl:my $cvs = Local::Cvsinfo->new();