From: Andreas Schwab <schwab@linux-m68k.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Thomas Adam <thomas@xteddy.org>,
John Wiegley <jwiegley@gmail.com>,
git@vger.kernel.org
Subject: Re: Please revert e371046b6473907aa6d62b7862a3afe9d33561e1
Date: Thu, 07 Jun 2012 19:07:27 +0200 [thread overview]
Message-ID: <m23967vynk.fsf@igel.home> (raw)
In-Reply-To: <7vd35bjcd6.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 07 Jun 2012 09:49:41 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> The way I read the log message of e371046b64 is that the repository
> resulting from the conversion without this patch will be different
> for repositories that were originally converted by the older
> cvs2git. So my impression is that it does not matter if the older
> tool died long time ago. As long as repositories converted by it
> still lives in the field, reverting the patch will start producing
> different (and arguably more correct) results for people who are
> using such a repository that started its life long time ago.
Only if the conversion is restarted from scratch. Otherwise, any
existing converted commits are preserved due to the incremental nature
of git cvsimport.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-06-07 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 10:28 Please revert e371046b6473907aa6d62b7862a3afe9d33561e1 John Wiegley
2012-06-06 17:41 ` Junio C Hamano
2012-06-06 17:54 ` Thomas Adam
2012-06-06 18:26 ` John Wiegley
2012-06-07 7:41 ` Michael Haggerty
2012-06-07 16:49 ` Junio C Hamano
2012-06-07 17:07 ` Andreas Schwab [this message]
2012-06-07 17:54 ` Junio C Hamano
2012-06-07 18:47 ` Andreas Schwab
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=m23967vynk.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jwiegley@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=thomas@xteddy.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.
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).