On Wed, Jan 2, 2013 at 5:41 PM, Eric S. Raymond <esr@xxxxxxxxxxx> wrote: > Martin Langhoff <martin.langhoff@xxxxxxxxx>: >> 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. > > I am extremely confident. I built a test suite so I could be. I too am glad to see some work go into the cvsimport script. So just to clear things up, previously you said this: > Yes, they must install an updated cvsps. This is the problem, and one that is easily "solved" by just keeping a copy of the old command. Remember that for many users of these tools it doesn't matter if the history is correct or not, as long as the head checkout contains the right files and they are able to submit new changes. With this definition of "works" git-cvsimport is not that broken I think. Cheers, - Thomas -- 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