From: Steinar Bang <sb@dod.no>
To: gdb@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: A Proposal to Move to Git
Date: Wed, 21 Aug 2013 18:40:00 -0000 [thread overview]
Message-ID: <87siy299bv.fsf@dod.no> (raw)
In-Reply-To: <83siy3jd7m.fsf@gnu.org>
>>>>> Eli Zaretskii <eliz@gnu.org>:
> . Files/directories that are deleted or moved/renamed. Will the
> information from the Attic be extracted, and will git be able to
> intuit renaming and handle deleted files correctly? (One type of
> file which we constantly rename is ChangeLog.)
If you mean follow the history with "git blame" and "git log" across
renames, then the answer is: it depends on how that rename is
represented in the CVS repository.
If a file is removed with one name, and the exact same file is added
with a different name, git itself should be able to detect this as a
rename, no matter what the conversion tool does.
But there are several ways to represent a rename in CVS... issue #1 for
cvs2svn (from which cvs2git derives) lists the possible ways a rename
can be done, and discusses the heuristics to detect this. I see that
this issue is still open:
http://cvs2svn.tigris.org/issues/show_bug.cgi?id=1
next prev parent reply other threads:[~2013-08-21 18:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 21:12 Tom Tromey
2013-08-20 21:16 ` Andrew Pinski
2013-08-20 21:26 ` Joseph S. Myers
2013-08-20 21:19 ` Joel Brobecker
2013-08-20 21:21 ` Paul_Koning
2013-08-20 22:59 ` Phil Muldoon
2013-08-21 15:05 ` Eli Zaretskii
2013-08-21 15:32 ` Andreas Schwab
2013-08-21 15:54 ` Eli Zaretskii
2013-08-26 8:05 ` Andreas Schwab
2013-08-21 18:40 ` Steinar Bang [this message]
2013-08-21 20:05 ` Eli Zaretskii
2013-08-21 20:38 ` Andreas Schwab
2013-08-22 18:56 ` Florian Weimer
2013-08-21 15:38 ` Steve Ellcey
2013-08-21 15:50 ` Joel Brobecker
2013-08-22 6:10 ` Tristan Gingold
2013-08-22 14:16 ` Richard Earnshaw
2013-08-22 14:25 ` Joel Brobecker
2013-08-22 14:39 ` Fred Cooke
2013-08-22 20:10 ` Mark Kettenis
2013-08-22 20:21 ` Fred Cooke
2013-08-22 20:22 ` David Miller
2013-08-22 20:48 ` Andrew Pinski
2013-08-22 21:07 ` Andreas Schwab
2013-08-22 21:10 ` Tom Tromey
2013-08-23 15:40 ` H.J. Lu
2013-08-23 15:55 ` Joel Brobecker
2013-08-23 16:03 ` Paul_Koning
2013-08-23 16:05 ` H.J. Lu
2013-08-26 12:37 ` NightStrike
[not found] ` <upzc38pvcv1w.fsf@dod.no>
2013-08-27 16:21 ` asmwarrior
2013-08-23 16:03 ` H.J. Lu
2013-08-23 16:09 ` Joel Brobecker
2013-08-23 16:24 ` Matt Rice
2013-08-23 16:37 ` H.J. Lu
2013-08-23 16:47 ` Matt Rice
2013-08-23 17:01 ` H.J. Lu
[not found] ` <87siy070su.fsf@dod.no>
2013-08-24 0:27 ` Doug Evans
2013-08-22 23:55 ` Alan Modra
2013-08-30 22:58 ` Hans-Peter Nilsson
2013-08-30 23:37 ` Joseph S. Myers
2013-08-31 2:05 ` Hans-Peter Nilsson
2013-08-31 16:58 ` Joseph S. Myers
2013-09-04 16:55 ` Doug Evans
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=87siy299bv.fsf@dod.no \
--to=sb@dod.no \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.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