Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

"Eric S. Raymond" writes: > Jeff King : >> I am not qualified to write on the current state of >> the art in CVS importing. > > I *am* qualified; cvs-fast-export has had a lot of work put into it by > myself and others over the last five years.

Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

On Tue, Sep 27, 2016 at 08:11:08PM -0400, Eric S. Raymond wrote: > Jeff King : > > I am not qualified to write on the current state of > > the art in CVS importing. > > I *am* qualified; cvs-fast-export has had a lot of work put into it by > myself and others over

Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

Jeff King : > I am not qualified to write on the current state of > the art in CVS importing. I *am* qualified; cvs-fast-export has had a lot of work put into it by myself and others over the last five years. Nobody else is really working this problem anymore, not

Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

On Thu, Sep 22, 2016 at 09:15:26AM -0400, Eric S. Raymond wrote: > Jeff King : > > Back when this guide was written, cvsimport was the only > > game in town. These days it is probably not the best option. > > It is absolutely not. As I have tried to point out here before, it > is

Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

Jeff King : > Back when this guide was written, cvsimport was the only > game in town. These days it is probably not the best option. It is absolutely not. As I have tried to point out here before, it is *severely* broken in its processing of branchy CVS repositories. Nobody

[PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

Back when this guide was written, cvsimport was the only game in town. These days it is probably not the best option. Rather than go into details, let's point people to the note at the top of cvsimport which gives other options. Signed-off-by: Jeff King ---