From: Chris Shoemaker <c.shoemaker@cox.net>
To: git@vger.kernel.org
Cc: cvsps@dm.cobite.com, David Mansfield <david@cobite.com>,
Martin Langhoff <martin@catalyst.net.nz>
Subject: CVSps fixed; git-cvsimport works, too
Date: Wed, 9 Nov 2005 20:41:06 -0500 [thread overview]
Message-ID: <20051110014106.GA19835@pe.Belkin> (raw)
In-Reply-To: <20051109222634.GA19209@pe.Belkin>
On Wed, Nov 09, 2005 at 05:26:34PM -0500, Chris Shoemaker wrote:
> I could cut git-cvsimport some slack for failing to infer that file
> 'b' is also on the 'dev' branch, since I learned how hard that is when
> I taught CVSps to make that inference. But completely missing a
> branch and all files added to it is not good.
Ok. Whew, I'm glad to report that I was mistaken. git-cvsimport
performs beautifully when given the new CVSps output. Sorry for the
noise.
I'll change this then to an announcement that with that CVSps patch,
CVSps produces more accurate branch ancestry, and git-cvsimport can
correctly reproduce branch-of-a-branch histories.
On a related note, the new '-P' option doesn't behave exactly as I
expected. You must provide the _full_ pathname to the input file
CVSps file. If that's not a bug, it should at least be documented.
-chris
prev parent reply other threads:[~2005-11-10 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 3:51 [OT] ancestor branch in cvsps is wrong for branch-of-branch Chris Shoemaker
2005-11-09 22:26 ` [PATCH] CVSps fixed, git-cvsimport still buggy (WAS: [OT] ancestor branch in cvsps is wrong for branch-of-branch) Chris Shoemaker
2005-11-10 1:41 ` Chris Shoemaker [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=20051110014106.GA19835@pe.Belkin \
--to=c.shoemaker@cox.net \
--cc=cvsps@dm.cobite.com \
--cc=david@cobite.com \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
/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