From: Heiko Voigt <hvoigt@hvoigt.net>
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: Sat, 29 Dec 2012 00:01:49 +0100 [thread overview]
Message-ID: <20121228230149.GA3575@book-mint> (raw)
In-Reply-To: <20121228162025.8565E4413A@snark.thyrsus.com>
Hi,
On Fri, Dec 28, 2012 at 11:20:25AM -0500, 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.
You mean: It does not build correctly with a current version of git?
Since it links with the git source code it probably needs a version of
gits source code around the time of the last commits.
Maybe you could add that information to the parsecvs compile
instructions? I think just because it takes some effort to compile does
not justify to remove this useful pointer here. When I was converting a
legacy cvs repository this pointer would have helped me a lot.
It is the tool we were/are actively using to convert old repositories at
$dayjob.
Cheers Heiko
next prev parent reply other threads:[~2012-12-28 23:02 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 [this message]
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
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=20121228230149.GA3575@book-mint \
--to=hvoigt@hvoigt.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.