On Thu, 2006-03-23 at 19:39 -0500, Chris Shoemaker wrote: > On Thu, Mar 23, 2006 at 09:03:06PM +0100, Jan-Benedict Glaw wrote: > > On Wed, 2006-03-22 17:28:23 -0800, Linus Torvalds <torvalds@xxxxxxxx> wrote: > > > On Wed, 22 Mar 2006, Linus Torvalds wrote: > > > > This one-liner to cvsps.c seems to make sure we have an ancestor branch > > > > for that "gdb-4.18-branch" branch, at least according to the cvsps output. > > > > > > The "git cvsimport" is still running, but at least it seems to be happily > > > running further past the point it broke earlier. > > > > I've started it once again, too, with the one-liner added to Debian > > unstable's version of cvsps: > > > > It seems there's a patch like > > http://www.gelato.unsw.edu.au/archives/git/0602/16278.html is missing? > > ...or we need a better cvsps. Shall I add it and try again / try to > > continue, or give up on it for now? Though it would be nice to have > > these two large and important source trees under GIT control :-) I'm busy writing a new import tool to get X into git; I've got it generating complete revision trees in memory, and dumping them in graphviz form. I'd sure be interested to see how well this works with other ancient and broken CVS trees. Once I've got it dealing with current X.org CVS correctly (or, at least, reasonably), I'll finish it up and get it to actually generate the repository. git://git.freedesktop.org/~keithp/parsecvs Usage is completely lame at present -- a list of ,v file names either on the command line or via stdin (one name per line). The .dot file is output on stdout, with some diagnostics on stderr. Pipe this through 'dot -Tsvg' and you'll get a .svg file which can be viewed with inkscape. They're generally immense... -- keith.packard@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part