First of all, I am at the same time a sad, nostalgic, and very happy that old cvsimport is getting replaced. On Wed, Jan 2, 2013 at 11:18 AM, Eric S. Raymond <esr@xxxxxxxxxxx> wrote: > Two of the three claims in this paragraph are false. The manual page > does not tell you what is true, which is that old cvsps will fuck up > every branch by putting the root point at the wrong place. And if you > call silently and randomly damaging imports getting work done, your > definitions of "work" and "done" are broken. The existing cvsps/cvsimport combo work for CVS repos with simple branches, and can track those over time. Replacement with something more solid is welcome, but until you are extremely confident of its handling of legacy setups... I would still provide the old cvsimport, perhaps in contrib. cheers, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- 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