From: Chris Packham <judge.packham@gmail.com>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove the suggestion to use parsecvs, which is currently broken.
Date: Tue, 01 Jan 2013 23:05:00 +1300 [thread overview]
Message-ID: <50E2B4CC.7050503@gmail.com> (raw)
In-Reply-To: <20121228162025.8565E4413A@snark.thyrsus.com>
Minor typo
On 12/29/2012 05:20 AM, Eric S. Raymond wrote:
> The parsecvs code has been neglected for a long time, and the only
> public version does not even build correctly. I have been handed
> control of the project and intend to fix this, but until I do it
> cannot be recommended.
>
> Also, the project URL given for Subversion needed to be updated
> to follow their site move.
> ---
> Documentation/git-cvsimport.txt | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
> index 98d9881..9d5353e 100644
> --- a/Documentation/git-cvsimport.txt
> +++ b/Documentation/git-cvsimport.txt
> @@ -213,11 +213,9 @@ Problems related to tags:
> * Multiple tags on the same revision are not imported.
>
> If you suspect that any of these issues may apply to the repository you
> -want to import consider using these alternative tools which proved to be
> -more stable in practice:
> +want to imort, consider using cvs2git:
s/imort/import/
>
> -* cvs2git (part of cvs2svn), `http://cvs2svn.tigris.org`
> -* parsecvs, `http://cgit.freedesktop.org/~keithp/parsecvs`
> +* cvs2git (part of cvs2svn), `http://subversion.apache.org/`
>
> GIT
> ---
>
prev parent reply other threads:[~2013-01-01 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 16:20 [PATCH] Remove the suggestion to use parsecvs, which is currently broken Eric S. Raymond
2012-12-28 19:28 ` Junio C Hamano
2012-12-28 23:01 ` Heiko Voigt
2012-12-29 4:42 ` Eric S. Raymond
2013-01-06 16:34 ` Heiko Voigt
2013-01-06 20:32 ` Eric S. Raymond
2013-01-07 19:21 ` Junio C Hamano
2013-01-07 20:41 ` Eric S. Raymond
2013-01-01 10:05 ` Chris Packham [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50E2B4CC.7050503@gmail.com \
--to=judge.packham@gmail.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
/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.
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).