From: David Kastrup <dak@gnu.org>
To: "Sokolov\, Konstantin \(ext\)" <konstantin.sokolov.ext@siemens.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: AW: Understanding behavior of git blame -M
Date: Sat, 16 Aug 2014 09:02:55 +0200 [thread overview]
Message-ID: <87sikwdihs.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <71BF70CE41AEE741896AF3A5450D86F11F28C786@DEFTHW99EH3MSX.ww902.siemens.net> (Konstantin Sokolov's message of "Fri, 15 Aug 2014 20:54:48 +0000")
"Sokolov, Konstantin (ext)" <konstantin.sokolov.ext@siemens.com> writes:
> Hi David,
>
> thank you very much for the exhaustive answer. The keyword "hunk" made
> me try a little bit more. So I realized that -M works as expected when
> at least three lines are moved.
>
> From your answer I discern that you find the current behavior
> correct.
I don't say any such thing and don't imply it.
--
David Kastrup
next prev parent reply other threads:[~2014-08-16 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 13:40 Understanding behavior of git blame -M Sokolov, Konstantin (ext)
2014-08-15 14:42 ` David Kastrup
2014-08-15 20:54 ` AW: " Sokolov, Konstantin (ext)
2014-08-16 7:02 ` David Kastrup [this message]
2014-08-16 0:06 ` Duy Nguyen
2014-08-15 17:07 ` Junio C Hamano
2014-08-15 20:57 ` AW: " Sokolov, Konstantin (ext)
2014-08-18 11:41 ` Sokolov, Konstantin (ext)
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=87sikwdihs.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=konstantin.sokolov.ext@siemens.com \
/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.