diff options
author | Junio C Hamano <gitster@pobox.com> | 2012-10-01 12:58:43 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2012-10-01 12:58:43 -0700 |
commit | 4dbf436bffdf43f91852e23018fc0e45c1bfdab8 (patch) | |
tree | dfcbe9afead80300a27047af8b099962f20e36f5 | |
parent | 03b98d2e78debf163d0dccc98a213dcd4608d7d8 (diff) | |
parent | e5dce96e9e26f8e30291c79fa5647313c64b2150 (diff) | |
download | git-4dbf436bffdf43f91852e23018fc0e45c1bfdab8.tar.gz git-4dbf436bffdf43f91852e23018fc0e45c1bfdab8.tar.xz |
Merge branch 'jc/blame-follows-renames'
Clarify the "blame" documentation to tell the users that there is
no need to ask for "--follow".
* jc/blame-follows-renames:
git blame: document that it always follows origin across whole-file renames
-rw-r--r-- | Documentation/git-blame.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt index 7ee923629..e44173f66 100644 --- a/Documentation/git-blame.txt +++ b/Documentation/git-blame.txt @@ -20,6 +20,12 @@ last modified the line. Optionally, start annotating from the given revision. The command can also limit the range of lines annotated. +The origin of lines is automatically followed across whole-file +renames (currently there is no option to turn the rename-following +off). To follow lines moved from one file to another, or to follow +lines that were copied and pasted from another file, etc., see the +`-C` and `-M` options. + The report does not tell you anything about lines which have been deleted or replaced; you need to use a tool such as 'git diff' or the "pickaxe" interface briefly mentioned in the following paragraph. |