log: Update log.follow doc and add to config.txt
Documentation/config.txt does not include the documentation for log.follow that is in Documentation/git-log.txt. This commit adds the log.follow documentation to config.txt and also updates the wording to be consistent with the format that is followed by other boolean configuration variables. Signed-off-by: Eric N. Vander Weele <ericvw@gmail.com> Acked-by: David Turner <dturner@twopensource.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Eric N. Vander Weele committed
Oct 6, 2015 at 21:14 UTC
fd8d07efdaf0ed5570f975c58b2ceb6500e06dd7
2 files changed
+10
-4
Documentation/config.txt
+6
@@ -1792,6 +1792,12 @@ log.decorate::
1792
specified, the full ref name (including prefix) will be printed.
1793
This is the same as the log commands '--decorate' option.
1794
1795
+log.follow::
1796
+ If `true`, `git log` will act as if the `--follow` option was used when
1797
+ a single <path> is given. This has the same limitations as `--follow`,
1798
+ i.e. it cannot be used to follow multiple files and does not work well
1799
+ on non-linear history.
1800
+
1801
log.showRoot::
1802
If true, the initial commit will be shown as a big creation event.
1803
This is equivalent to a diff against an empty tree.
Documentation/git-log.txt
+4
-4
@@ -185,10 +185,10 @@ log.date::
185
dates like `Sat May 8 19:35:34 2010 -0500`.
186
187
log.follow::
188
- If a single <path> is given to git log, it will act as
189
- if the `--follow` option was also used. This has the same
190
- limitations as `--follow`, i.e. it cannot be used to follow
191
- multiple files and does not work well on non-linear history.
188
+ If `true`, `git log` will act as if the `--follow` option was used when
189
+ a single <path> is given. This has the same limitations as `--follow`,
190
+ i.e. it cannot be used to follow multiple files and does not work well
191
+ on non-linear history.
192
193
log.showRoot::
194
If `false`, `git log` and related commands will not treat the