On Tue, Jul 04, 2006 at 11:15:47AM +1200, Martin Langhoff wrote: > Elrond, > > you are right, the current git-cvsimport takes a very naive approach > to determine where branches open from. It uses cvsps internally, which > only reports on the ancestor branch, so we take the latest commit from > the ancestor. If there is no fix visible, it probably should be documented, that git-cvsimport isn't the perfect solution, so people aren't surprised. > Parsecvs probably has a more sophisticated approach, have you tried it? After finding the current correct git:-url [1] for it, I noticed, that I need libgit for it (I use git from my distribution), so I've postponed this. Of course, you can use my script and try parsecvs yourself. > If the cvs2svn documentation is not lying, it probably has the > smartest/correctest implementation. For small-medium repos, you may be > able to run cvs2svn and then import with git-svnimport. I'll try that soon. Elrond [1] git://anongit.freedesktop.org/git/users/keithp/parsecvs - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Tue Jul 04 20:47:07 2006
This archive was generated by hypermail 2.1.8 : 2006-07-04 20:47:34 EST