diff options
author | David Turner <dturner@twopensource.com> | 2015-07-07 21:29:34 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2015-07-09 10:24:23 -0700 |
commit | 076c98372e7d3c86d269c1526349a67b73904330 (patch) | |
tree | 999e92b02a98156cc486a948d43edce28b106aa8 /Documentation/git-log.txt | |
parent | 5bdb7a78adf2a2656a1915e6fa656aecb45c1fc3 (diff) | |
download | git-076c98372e7d3c86d269c1526349a67b73904330.tar.gz |
log: add "log.follow" configuration variable
People who work on projects with mostly linear history with frequent
whole file renames may want to always use "git log --follow" when
inspecting the life of the content that live in a single path.
Teach the command to behave as if "--follow" was given from the
command line when log.follow configuration variable is set *and*
there is one (and only one) path on the command line.
Signed-off-by: David Turner <dturner@twopensource.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-log.txt')
-rw-r--r-- | Documentation/git-log.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt index 5692945a0b..97b9993ee8 100644 --- a/Documentation/git-log.txt +++ b/Documentation/git-log.txt @@ -184,6 +184,12 @@ log.date:: `--date` option.) Defaults to "default", which means to write dates like `Sat May 8 19:35:34 2010 -0500`. +log.follow:: + If a single <path> is given to git log, it will act as + if the `--follow` option was also used. This has the same + limitations as `--follow`, i.e. it cannot be used to follow + multiple files and does not work well on non-linear history. + log.showRoot:: If `false`, `git log` and related commands will not treat the initial commit as a big creation event. Any root commits in |