CVS's branch does not appear on cvsps's output, until you do a commit to it. git-cvsimport relies on cvsps and can not do much about this... Last problem may arise, if you try to do incremental imports from cvs to git. For incremental imports you must start import from same location in cvs each time. If you have made first import from beginning of history, sequent imports must start from there too. Otherwise cvsps will renumber patch sets. Tomi. On Sun, Nov 2, 2008 at 11:03 PM, Francis Galiegue <fg@xxxxxxxxxxxx> wrote: > Maybe it's due to the other bug that I reported with git-cvsimport a few days > ago: namely, it does NOT see branches created by CVS with no commits in them > (ie, create the branch and that's it, don't touch anything). > > The problem is very serious, since it seems to trigger another bug which > prevents git-cvsimport from working at all. cvsps DOES see the commit > correctly (branc exists for this file at 1.47.6): > > --- > Members: > > src/java/com/one2team/database/bean/impl/relation/reporting/Register.java:1.47->1.47.6.1 > --- > > But on the imported git repository, the diff is rather 1.60 -> 1.47.6.1! As a > result, the repository is plain unusable. > > As to the first problem, git finds 6 branches, cvs log finds 8 for the same > module. git finds 22 tags, cvs log finds 29! > > -- > fge > -- > 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 > -- 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
