Re: parsecvs tool now creates git repositories

From: Keith Packard <>
Date: 2006-04-04 00:37:27
On Mon, 2006-04-03 at 16:03 +0200, Erik Mouw wrote:
> On Sat, Apr 01, 2006 at 09:36:28PM -0800, Keith Packard wrote:
> > The UI is a total disaster, sufficient for testing. You must create an
> > Authors file in the current directory which looks like the git-cvsimport
> > authors file. You must also have a edit-change-log program in your path
> > which edits the commit message in place. /bin/true will work if you
> > don't need to edit the messages.
> > 
> > I should clearly steal the existing git-cvsimport command line arguments
> > and use those.
> What is the current way to use it? I get the impression it reads raw ,v
> files, but how do I get along with a remote CVS repository?

You can't. You need to create a local copy of the repository. There is a
tool which can do that using the cvs protocol, but I don't recall the

It turns out that parsing the ,v files directly is both faster and more
accurate than attempting to interpret the output of cvs log.


To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Received on Tue Apr 04 00:38:10 2006

This archive was generated by hypermail 2.1.8 : 2006-04-04 00:41:27 EST