* Magnus Hagander <magnus@hagander.net> [100109 13:05]:
> On Sat, Jan 9, 2010 at 18:33, Aidan Van Dyk <aidan@highrise.ca> wrote:
> > * Magnus Hagander <magnus@hagander.net> [100109 12:03]:
> >
> >> If that's the only remaining obstacle, I'm willing to work up some
> >> test scripts around that. But I'm not going to do that if it's going
> >> to fall over on something else as well, because it'll be a nontrivial
> >> amount of work to test ir properly :-)
> >
> > It's already been done. It was not a lot of work (just processor time).
> > It's even already been posted to -hackers, including what the
> > differences were (i.e. which $Tags$ differed, and where, and where the
> > CVS history had been hacked by hand).
>
> Do you still have the scripts?
Well, I have a screen running yet with bash history showing most of the
commands...
Basically, with a local $CVSROOT, import every tag/release/branch you want
into git as a tree:for b in $(cat ../tags.txt); do echo $b; rm -Rf * .git/index; cvs export -kk -r $b -d ./ pgsql >
/dev/null&& git add --all && git tag -f cvs-tag-$b $(git write-tree); done
And then, it's a simple matter of letting git diff the git ref with the corespnding CVS export tree them:for b in $(cat
../tags.txt);do echo $b; git diff $b cvs-tag-$b > /tmp/pg-parsecvs-$b.diff; done
a.
--
Aidan Van Dyk Create like a god,
aidan@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
