git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Fwd: git-cvsimport documentation improvement
       [not found] <CAOnWdogqShYMmZLAYvGnKVLdxPj8fYy4a2BZ-Mhe-kSKqQhv9Q@mail.gmail.com>
@ 2021-05-09  7:30 ` Reuben Thomas
  2021-05-09  8:39   ` Junio C Hamano
  0 siblings, 1 reply; 3+ messages in thread
From: Reuben Thomas @ 2021-05-09  7:30 UTC (permalink / raw)
  To: git

The git-cvsimport docs say:

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
cvs2git or cvs-fast-export.

However, I can find no trace of cvsps version 3. The latest seems to
be 2.2, which is marked as a pre-release, and cvsps 2.1 seems to be
the most commonly packaged version.

I understand that it's still better to use other tools than git
cvsimport, but perhaps the warning could be better worded; for
example:

WARNING: git cvsimport uses cvsps, which is considered deprecated. If
you are performing a one-shot import of a CVS repository consider
using cvs2git or cvs-fast-export.

-- 
https://rrt.sc3d.org

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Fwd: git-cvsimport documentation improvement
  2021-05-09  7:30 ` Fwd: git-cvsimport documentation improvement Reuben Thomas
@ 2021-05-09  8:39   ` Junio C Hamano
  2021-05-09 18:05     ` Eric Sunshine
  0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2021-05-09  8:39 UTC (permalink / raw)
  To: Reuben Thomas; +Cc: git

Reuben Thomas <rrt@sc3d.org> writes:

> The git-cvsimport docs say:
>
> 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
> cvs2git or cvs-fast-export.
>
> However, I can find no trace of cvsps version 3. The latest seems to
> be 2.2, which is marked as a pre-release, and cvsps 2.1 seems to be
> the most commonly packaged version.
>
> I understand that it's still better to use other tools than git
> cvsimport, but perhaps the warning could be better worded; for
> example:
>
> WARNING: git cvsimport uses cvsps, which is considered deprecated. If
> you are performing a one-shot import of a CVS repository consider
> using cvs2git or cvs-fast-export.

The text comes from this commit early in 2013.  Perhaps there was
cvsps 3 back then?


commit 1187ec99b93aefc3bfb6e360d285245745e1e390
Author: John Keeping <john@keeping.me.uk>
Date:   Thu Jan 24 19:18:45 2013 +0000

    git-cvsimport.txt: cvsps-2 is deprecated
    
    git-cvsimport relies on version 2 of cvsps and does not work with the
    new version 3.  Since cvsps 3.x does not currently work as well as
    version 2 for incremental import, document this fact.
    
    Specifically, there is no way to make new git-cvsimport that supports
    cvsps 3.x and have a seamless transition for existing users since cvsps
    3.x needs a time from which to continue importing and git-cvsimport does
    not save the time of the last import or import into a specific namespace
    so there is no safe way to calculate the time of the last import.
    
    Signed-off-by: John Keeping <john@keeping.me.uk>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
index 98d9881d7e..fd1e613d95 100644
--- a/Documentation/git-cvsimport.txt
+++ b/Documentation/git-cvsimport.txt
@@ -18,6 +18,12 @@ 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
+link:http://cvs2svn.tigris.org/cvs2git.html[cvs2git] or
+link:https://github.com/BartMassey/parsecvs[parsecvs].
+
 Imports a CVS repository into git. It will either create a new
 repository, or incrementally import into an existing one.
 

Search engine found this hit for "cvsps version 3"

    https://archlinux.org/packages/extra/x86_64/cvsps/

which suggested that another place to be looked at, which was

    https://aur.archlinux.org/packages/cvsps/

which then led to

    http://www.catb.org/esr/cvsps/

In any case, at this point both 2 and 3 haven't seen any active
maintenance for quite some time.



^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: Fwd: git-cvsimport documentation improvement
  2021-05-09  8:39   ` Junio C Hamano
@ 2021-05-09 18:05     ` Eric Sunshine
  0 siblings, 0 replies; 3+ messages in thread
From: Eric Sunshine @ 2021-05-09 18:05 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: Reuben Thomas, Git List

On Sun, May 9, 2021 at 4:39 AM Junio C Hamano <gitster@pobox.com> wrote:
> Reuben Thomas <rrt@sc3d.org> writes:
> > The git-cvsimport docs say:
> >
> > 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
> > cvs2git or cvs-fast-export.
> >
> > However, I can find no trace of cvsps version 3. The latest seems to
> > be 2.2, which is marked as a pre-release, and cvsps 2.1 seems to be
> > the most commonly packaged version.
>
> The text comes from this commit early in 2013.  Perhaps there was
> cvsps 3 back then?

There's a cvsps 3.13, but it's deprecated and was EOL'd at the end of 2013.
http://www.catb.org/~esr/cvsps/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-05-09 18:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAOnWdogqShYMmZLAYvGnKVLdxPj8fYy4a2BZ-Mhe-kSKqQhv9Q@mail.gmail.com>
2021-05-09  7:30 ` Fwd: git-cvsimport documentation improvement Reuben Thomas
2021-05-09  8:39   ` Junio C Hamano
2021-05-09 18:05     ` Eric Sunshine

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).