On 5/30/06, Donnie Berkholz <spyderous@xxxxxxxxxx> wrote:
All I can think of is that I somehow OOM'd when I manually ran a repack and didn't notice it. But that should've at least made me unable to resume the cvsimport process, which happily kept chugging along later on.
Sounds likely -- and cvsimport restarts gracefully, though you might want to do git checkout HEAD to get a usable checkout if the very first import failed. However, the default head is master, and what you want to look at is origin or whatever you passed as your -o parameter. I use cvshead normally, so I do git log cvshead
> My dmesg talks about an earlier cvs segfault. Nasty tree you have here > -- it's breaking all sorts of things... and teaching us a thing or two > about the import process. > >> Committed patch 249100 (origin 2005-08-20 05:05:58) > > Hmmm? How can you be at patch 249100 and still be a good year ahead of > me? Have you told cvsps to cut off old history? Nope. I ran the exact cvsps flags you posted earlier to create it.
Oh, that was an earlier PEBKAK at my end: I did git log HEAD instead of git log cvshead. My import is now at 293145 (cvshead +0000 2005-12-25 12:24:42) which looks promising. cheers, martin - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html