From: Johannes Sixt <j.sixt@viscovery.net>
To: Yuri D'Elia <wavexx@users.sf.net>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Bernardo Innocenti <bernie@codewiz.org>
Subject: Re: rename tracking and file-name swapping
Date: Mon, 14 Sep 2009 08:44:37 +0200 [thread overview]
Message-ID: <4AADE655.60503@viscovery.net> (raw)
In-Reply-To: <1248088D-85CB-4335-AD8A-07DB5BAD1AAA@users.sf.net>
Yuri D'Elia schrieb:
> On 13 Sep 2009, at 20:14, Junio C Hamano wrote:
>> By default, if the pathname that was present in the old version still
>> appears in the new version, that path is not considered as a candiate
>> for rename detection. Only "X used to be there but is gone" and "Y did
>> not exist but appeared" are paired up and checked if they are similar.
>>
>> Give the command -B option, too, to break the filepair that does not
>> disappear.
>
> That does the trick. I'm curious, is there any other use for -B besides
> rename handling?
Yes: It can make patches easier to read (just like -M and -C do) if a file
was completely rewritten. For example, look at b9dfe51c with and without
-B, and also note the "dissimilarity index" in the diff header.
-- Hannes
next prev parent reply other threads:[~2009-09-14 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 11:17 rename tracking and file-name swapping Yuri D'Elia
2009-09-13 18:14 ` Junio C Hamano
2009-09-13 21:13 ` Yuri D'Elia
2009-09-14 6:44 ` Johannes Sixt [this message]
2009-09-15 3:34 ` [Bug?] "diff -B --color" output doesn't show space errors Nanako Shiraishi
2009-09-15 4:44 ` Junio C Hamano
2009-09-15 5:05 ` [PATCH] diff --whitespace: fix blank lines at end Junio C Hamano
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=4AADE655.60503@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=bernie@codewiz.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=wavexx@users.sf.net \
/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.