git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats
Date: Wed, 28 Sep 2016 10:59:05 -0700	[thread overview]
Message-ID: <xmqqlgybkis6.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160928001108.GA9120@thyrsus.com> (Eric S. Raymond's message of "Tue, 27 Sep 2016 20:11:08 -0400")

"Eric S. Raymond" <esr@thyrsus.com> writes:

> Jeff King <peff@peff.net>:
>>               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 much else than cvs2git is even left
> standing at this point.

It sounds like you, as a better qualified person, would be in the
best position to send an update to the documentation to tell people
not to use older and unmaintained ones and guides them instead to a
newer and better tool.

    ... ah, I notice that peff said the same already.

I'd be fine with reviewing and applying such a patch.

Thanks.

      parent reply	other threads:[~2016-09-28 17:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  7:23 [PATCH 0/3] update git cvs import documentation Jeff King
2016-09-22  7:25 ` [PATCH 1/3] docs/cvsimport: prefer cvs-fast-export to parsecvs Jeff King
2016-09-22  7:26 ` [PATCH 2/3] docs/cvs-migration: update link to cvsps homepage Jeff King
2016-09-22  7:26 ` [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats Jeff King
2016-09-22 13:15   ` Eric S. Raymond
2016-09-23  3:56     ` Jeff King
2016-09-28  0:11       ` Eric S. Raymond
2016-09-28  6:41         ` Jeff King
2016-09-28 17:59         ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqlgybkis6.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=esr@thyrsus.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).