commit | e5dce96e9e26f8e30291c79fa5647313c64b2150 | [log] [tgz] |
---|---|---|
author | Junio C Hamano <gitster@pobox.com> | Fri Sep 21 12:09:42 2012 -0700 |
committer | Junio C Hamano <gitster@pobox.com> | Fri Sep 21 12:14:19 2012 -0700 |
tree | 6d97672b00d1778df96c99b962be6396b532407f | |
parent | bafc478f1618534fcb85bedc0fa224bd2d462441 [diff] |
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>