From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Git Mailinglist <git@vger.kernel.org>
Subject: git blame not respecting --find-copies-harder ?
Date: Wed, 30 Jul 2008 11:39:03 +0200 [thread overview]
Message-ID: <20080730093903.GA14330@cuci.nl> (raw)
git clone git://git.cuci.nl/pike
Both of this "git blame" commands return the same (erroneous) results
at the end of the files (the last lines are older, and are from the old
README file next to it).
git blame README-CVS
git blame --find-copies-harder README-CVS
However, when using git show with and without --find-copies-harder, we
see that git indeed finds the copy with a 76% similarity index.
git show 9eb55816
git show --find-copies-harder 9eb55816
Shouldn't it be expected that blame should also give the same difference
in result with and without that option?
On a related note, it doesn't seem possible to make --find-copies-harder
a default; is that intentional?
--
Sincerely,
Stephen R. van den Berg.
How many weeks are there in a lightyear?
next reply other threads:[~2008-07-30 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 9:39 Stephen R. van den Berg [this message]
2008-07-30 15:01 ` git blame not respecting --find-copies-harder ? Björn Steinbrink
2008-07-30 15:43 ` Sverre Rabbelier
2008-07-31 6:48 ` Jeff King
2008-07-31 7:05 ` Junio C Hamano
2008-07-31 7:21 ` Jeff King
2008-07-31 7:36 ` Junio C Hamano
2008-07-31 8:25 ` Jeff King
2008-07-31 8:35 ` Junio C Hamano
2008-07-31 9:01 ` Pierre Habouzit
2008-07-31 9:05 ` Jeff King
2008-07-31 9:06 ` Pierre Habouzit
2008-07-31 9:03 ` Jeff King
2008-07-31 9:15 ` Pierre Habouzit
2008-07-31 9:34 ` Jeff King
2008-07-31 10:22 ` Pierre Habouzit
2008-07-31 10:33 ` Jeff King
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=20080730093903.GA14330@cuci.nl \
--to=srb@cuci.nl \
--cc=git@vger.kernel.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).