From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: How to verify that lines were only moved, not edited?
Date: Thu, 20 Oct 2011 08:20:23 +0200 [thread overview]
Message-ID: <4E9FBDA7.3000904@viscovery.net> (raw)
In-Reply-To: <20111019163354.GB3157@sigill.intra.peff.net>
Am 10/19/2011 18:33, schrieb Jeff King:
> git init
> seq 1 5000 >foo
> git add foo
> git commit -m initial
> sed -i '/^2..$/d' foo
> seq 200 299 >>foo
> git commit -a -m 'move 200-299 to end'
>
> I get the expected result from "git blame -M" (i.e., everything
> attributed to the root commit).
I see. My example is more like this:
for i in `seq 1 20`; do md5sum - <<< $i; done > foo
git commit -a -m foo
for i in `seq 1 20`; do md5sum - <<< $i; done | sort > foo
git commit -a -m foo\ sorted
i.e., the sort order of a block of lines was changed "in place". Here,
most of the lines are attributed to the last commit. Am I expecting too
much from git-blame to detect line motions in such a case?
-- Hannes
next prev parent reply other threads:[~2011-10-20 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:34 How to verify that lines were only moved, not edited? Johannes Sixt
2011-10-19 16:33 ` Jeff King
2011-10-20 6:20 ` Johannes Sixt [this message]
2011-10-19 17:07 ` Junio C Hamano
2011-10-20 6:25 ` Johannes Sixt
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=4E9FBDA7.3000904@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.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 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).