On Tue, Oct 7, 2008 at 01:08, Andreas Ericsson <ae@xxxxxx> wrote: > Has the CVS repo been tampered with in the past? If so, it's entirely > possible that checking out and working with CVS works just fine, but > getting history into coherent changesets is impossible. Unfortunately yes. Thats what I thought, and was afraid, was going on. I've managed to get things working by restoring some of the missing files ,v files from a backup and regenerating the tracking repositories. Then I had to remove the files in question from cvs and readd them, git cvsimport then saw these files. > cvs2svn is apparently quite good at getting even the weirdest history > right. Perhaps you can try that and then running "git svn" on the > resulting svn repo? Thanks, I'll give cvs2svn a go. > Good luck. You'll probably need it :-/ Cheers Adam -- To unsubscribe from this list: 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
