First, <since> and <until> are ways to specify "revisions", not
"commits", as gitrevisions.txt would indicate. Second,
'<since>..<until>' is simply indicative of how users would normally
want to specify the rev spec: it need not conform to this form, and
can take any form that gitrevisions.txt lists. A 'git log :/quuxery'
is perfectly valid, for instance. Make these two corrections to the
description of '<since>..<until>' under OPTIONS.
Signed-off-by: Ramkumar Ramachandra <artag...@gmail.com>
---
Documentation/git-log.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 69db578..f03ae74 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -25,11 +25,11 @@ OPTIONS
-------
<since>..<until>::
- Show only commits between the named two commits. When
+ Show only commits between the named two revisions. When
either <since> or <until> is omitted, it defaults to
`HEAD`, i.e. the tip of the current branch.
- For a more complete list of ways to spell <since>
- and <until>, see linkgit:gitrevisions[7].
+ For a more complete list of ways to spell <since>..<until>,
+ see linkgit:gitrevisions[7].
--follow::
Continue listing the history of a file beyond renames
--
1.8.2.1.506.gbce9ff0
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
