From: Michael Haggerty <mhagger@alum.mit.edu>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Best way to merge two repos with same content, differenthistory
Date: Fri, 19 Jun 2009 11:52:59 +0200 [thread overview]
Message-ID: <4A3B5FFB.1030001@alum.mit.edu> (raw)
In-Reply-To: <robbat2-20090605T194802-473902673Z@orbis-terrarum.net>
Robin H. Johnson wrote:
> [Regarding cvs2git] In doing so discovered a testcase where RCSRevisionReader and
> CVSRevisionReader gave different output themselves, the latter (which is
> documented as more accurate otherwise) missing the contents of an entire
> file. It's on the cvs2svn-dev mailing list now. Tracing that first,
> thereafter comparing it to the new Git side.
In case anybody is following this, the issue that Robin found was in
release 2.2.0 of cvs2svn/cvs2git, but had already been fixed in the
current trunk version...
Conclusion 1: Please use the trunk version of cvs2git, not release
2.2.0. Trunk is usually the most stable version available, especially
for 2git conversions.
Conclusion 2: I've really got to get around to making a new release :-/
Michael
next prev parent reply other threads:[~2009-06-19 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 16:30 Best way to merge two repos with same content, different history Kelly F. Hickel
2009-06-05 16:53 ` Rostislav Svoboda
2009-06-05 17:10 ` Kelly F. Hickel
2009-06-05 17:19 ` Rostislav Svoboda
2009-06-05 18:46 ` Robin H. Johnson
2009-06-05 19:06 ` Best way to merge two repos with same content, differenthistory Kelly F. Hickel
2009-06-05 20:02 ` Robin H. Johnson
2009-06-05 20:08 ` Kelly F. Hickel
2009-06-19 9:52 ` Michael Haggerty [this message]
2009-06-05 17:01 ` Best way to merge two repos with same content, different history Avery Pennarun
2009-06-05 17:11 ` Kelly F. Hickel
2009-06-05 17:15 ` Markus Heidelberg
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=4A3B5FFB.1030001@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=robbat2@gentoo.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).