| commit | e5dce96e9e26f8e30291c79fa5647313c64b2150 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Fri, 21 Sep 2012 19:09:42 +0000 (21 12:09 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 21 Sep 2012 19:14:19 +0000 (21 12:14 -0700) | ||
| tree | 6d97672b00d1778df96c99b962be6396b532407f | treesnapshot (tar.gz zip) |
| parent | bafc478f1618534fcb85bedc0fa224bd2d462441 | commitdiff |
git blame: document that it always follows origin across whole-file renames
Make it clear to people who (rightly or wrongly) think that the
"--follow" option should follow origin across while-file renames
that we already do so. That would explain the output that they see
when they do give the "--follow" option to the command.
We may or may not want to do a "--no-follow" patch as a follow-up,
but that is a separate topic.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Make it clear to people who (rightly or wrongly) think that the
"--follow" option should follow origin across while-file renames
that we already do so. That would explain the output that they see
when they do give the "--follow" option to the command.
We may or may not want to do a "--no-follow" patch as a follow-up,
but that is a separate topic.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-blame.txt | diffblobblamehistory |