Le Monday 03 November 2008 10:31:59 Francis Galiegue, vous avez écrit : > Hello, > > As I am keen to make my company use git eventually, but they have a really, > really messy CVS tree that git-cvs*.perl cannot handle right now, I've > decided to have a serious look at the code. > As stated in one mail I sent earlier on, the real problem is that git-cvsimport won't detect empty branches for two reasons: * it relies on cvsps output, which doesn't tell about it either; * however, it doesn't make use of another file that cvsps generates in $HOME/.cvsps by default, which can help about giving this information. I'll try the following: * instead of capturing cvsps output directly, I'll use its -p option, which has the advantage of generating one file per patchset; * I'll consolidate the information of the other generated file in a hash and correlate the information found in there with the individual patchset: my hope is that I'll be able to detect so-far undetected branches and create them. -- Francis Galiegue ONE2TEAM Ingénieur système Mob : +33 (0) 6 83 87 78 75 Tel : +33 (0) 1 78 94 55 52 fge@xxxxxxxxxxxx 40 avenue Raymond Poincaré 75116 Paris -- 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
