Re: git-cvsimport BUG: some commits are completely out of phase (but cvsps sees them all right)

[Francis Galiegue <fg@one2team.net>]

Le Sunday 02 November 2008 23:21:44 Tomi Pakarinen, vous avez écrit :
> CVS's branch does not appear on cvsps's output, until you do a commit
> to it. git-cvsimport
> relies on cvsps and can not do much about this...
>

Well, there's another file that cvsps generate (in $HOME/.cvsps) that helps 
here and that is named ":<method>:<method_args>:#path#to#cvsroot#modulename." 
This file contains the needed information. As far as I can see though, 
git-cvsimport does not use it.


> Last problem may arise, if you try to do incremental imports from cvs to
> git. For incremental imports you must start import from same location in
> cvs each time.
> If you have made first import from beginning of history, sequent
> imports must start
> from there too. Otherwise cvsps will renumber patch sets.
>

The plan would be to convert all modules in one go, with no one committing in 
the meantime, so that's not a problem.

I'll try and dig a little deeper into git-cvsimport and see if I can make it 
use this information...

-- 
fge