git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Wong <andrew.kw.w@gmail.com>
To: git@vger.kernel.org
Subject: blame -C: adding a line in moved content sometimes affect blame result
Date: Wed, 08 Jun 2011 01:09:46 -0400	[thread overview]
Message-ID: <4DEF041A.9070003@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 452 bytes --]

I've attached a script for illustration.

After moving content from file1 to file2, "git blame -C file2" correctly 
shows that the content came from file1. However, if I add a line in near 
the top or bottom of the moved content in file2, "git blame -C file2" 
fails to detect that the top or bottom of the moved contents came from 
file1. I looked around in blame.c, and this feels like a boundary case 
somewhere inside find_copy_in_blob? Any clues?

[-- Attachment #2: blame_issue.sh --]
[-- Type: application/x-sh, Size: 1060 bytes --]

             reply	other threads:[~2011-06-08  5:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  5:09 Andrew Wong [this message]
2011-06-09  1:31 ` blame -C: adding a line in moved content sometimes affect blame result Andrew Wong
2011-06-09  3:25 ` 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=4DEF041A.9070003@gmail.com \
    --to=andrew.kw.w@gmail.com \
    --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).