git-log.txt: generalize <since>..<until>
'<since>..<until>' is misleading, as there are many other forms that 'git log' can accept as an argument. Replace it with <revision range>, referring to the section "Specifying Ranges" in revisions.txt, and rewrite the section appropriately. Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ramkumar Ramachandra committed
Apr 22, 2013 at 11:00 UTC
21a40b90e9189aa3f3fbae1ca7a4bad55028ed03
1 file changed
+9
-7
Documentation/git-log.txt
+9
-7
@@ -9,7 +9,7 @@ git-log - Show commit logs
9
SYNOPSIS
10
--------
11
[verse]
12
-'git log' [<options>] [<since>..<until>] [[\--] <path>...]
12
+'git log' [<options>] [<revision range>] [[\--] <path>...]
13
14
DESCRIPTION
15
-----------
@@ -62,12 +62,14 @@ produced by --stat etc.
62
Note that only message is considered, if also a diff is shown
63
its size is not included.
64
65
-<since>..<until>::
66
- Show only commits between the named two commits. When
67
- either <since> or <until> is omitted, it defaults to
68
- `HEAD`, i.e. the tip of the current branch.
69
- For a more complete list of ways to spell <since>
70
- and <until>, see linkgit:gitrevisions[7].
65
+<revision range>::
66
+ Show only commits in the specified revision range. When no
67
+ <revision range> is specified, it defaults to `HEAD` (i.e. the
68
+ whole history leading to the current commit). `origin..HEAD`
69
+ specifies all the commits reachable from the current commit
70
+ (i.e. `HEAD`), but not from `origin`. For a complete list of
71
+ ways to spell <revision range>, see the "Specifying Ranges"
72
+ section of linkgit:gitrevisions[7].
73
74
[\--] <path>...::
75
Show only commits that are enough to explain how the files