Documentation: clarify effects of -- <path> arguments
'git log -- <path>' does not "show commits that affect the specified paths" in a literal sense unless --full-history is given (for example, a file that only existed on a side branch will turn up no commits at all!). Reword it to specify the actual intent of the filtering, and point to the "History Simplification" section. Signed-off-by: Thomas Rast <trast@student.ethz.ch> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thomas Rast committed
Aug 30, 2011 at 11:21 UTC
b15b5b10a75e202f3f90e000925545243267cbee
1 file changed
+7
-4
Documentation/git-log.txt
+7
-4
@@ -69,10 +69,13 @@ produced by --stat etc.
69
its size is not included.
70
71
[\--] <path>...::
72
- Show only commits that affect any of the specified paths. To
73
- prevent confusion with options and branch names, paths may need
74
- to be prefixed with "\-- " to separate them from options or
75
- refnames.
72
+ Show only commits that are enough to explain how the files
73
+ that match the specified paths came to be. See "History
74
+ Simplification" below for details and other simplification
75
+ modes.
76
++
77
+To prevent confusion with options and branch names, paths may need to
78
+be prefixed with "\-- " to separate them from options or refnames.
79
80
include::rev-list-options.txt[]
81