From: Junio C Hamano <hidden> Date: 2016-06-15 22:55:52
John Keeping [off-list ref] writes:
quoted hunk
My preference would be for something like this, possibly with an
expanded examples section showing how to pipe the output of cvsps-3 or
cvs2git into git-fast-import:
-- >8 --
@@ -18,6 +18,11 @@ SYNOPSIS DESCRIPTION -----------+*WARNING:* `git cvsimport` uses cvsps version 2, which is considered+deprecated; it does not work with cvsps version 3 and later. If you are+performing a one-shot import of a CVS repository consider using cvsps-3,+cvs2git or parsecvs directly.+ Imports a CVS repository into git. It will either create a new repository, or incrementally import into an existing one.-- 8< --
OK, that is certainly a lot simpler to explain.
Is it "it does not work yet with cvsps3", or "it will not ever work
with cvsps3"? The impression I am getting is that it is the latter.
Also, should we have a suggestion to people who are *not* performing
a one-shot import, i.e. doing incremental or bidirectional?
From: John Keeping <hidden> Date: 2016-06-15 22:55:52
On Wed, Jan 23, 2013 at 09:13:27AM -0800, Junio C Hamano wrote:
John Keeping [off-list ref] writes:
quoted
My preference would be for something like this, possibly with an
expanded examples section showing how to pipe the output of cvsps-3 or
cvs2git into git-fast-import:
-- >8 --
@@ -18,6 +18,11 @@ SYNOPSIS DESCRIPTION -----------+*WARNING:* `git cvsimport` uses cvsps version 2, which is considered+deprecated; it does not work with cvsps version 3 and later. If you are+performing a one-shot import of a CVS repository consider using cvsps-3,+cvs2git or parsecvs directly.+ Imports a CVS repository into git. It will either create a new repository, or incrementally import into an existing one.-- 8< --
OK, that is certainly a lot simpler to explain.
Is it "it does not work yet with cvsps3", or "it will not ever work
with cvsps3"? The impression I am getting is that it is the latter.
The existing script (git-cvsimport.perl) won't ever work with cvsps-3
since features it relies on have been removed.
Also, should we have a suggestion to people who are *not* performing
a one-shot import, i.e. doing incremental or bidirectional?
As far as I know cvsps is the only backend that attempts to support
partial exports but the support for that in its fast-export mode needs
work before I would consider it reliable. For now the existing
git-cvsimport is the best option I'm aware of.
John
From: Chris Rorvick <hidden> Date: 2016-06-15 22:55:53
On Wed, Jan 23, 2013 at 3:12 PM, John Keeping [off-list ref] wrote:
The existing script (git-cvsimport.perl) won't ever work with cvsps-3
since features it relies on have been removed.
Not reporting the ancestry branch seems to be the big one. Are there
others? I had a version of the Perl script sort of working, but only
well enough to pass the t9600 and t9604 tests.
Chris
From: John Keeping <hidden> Date: 2016-06-15 22:55:53
On Thu, Jan 24, 2013 at 10:55:57PM -0600, Chris Rorvick wrote:
On Wed, Jan 23, 2013 at 3:12 PM, John Keeping [off-list ref] wrote:
quoted
The existing script (git-cvsimport.perl) won't ever work with cvsps-3
since features it relies on have been removed.
Not reporting the ancestry branch seems to be the big one. Are there
others?
For some reason I thought the non-fast-export output mode had already
been removed, but now that I check it looks like it's still there just
with a warning that it may be removed in the future.
John