'<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 <artag...@gmail.com>
 Documentation/git-log.txt | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 64cc337..c238475 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -9,7 +9,7 @@ git-log - Show commit logs
-'git log' [<options>] [<since>..<until>] [[\--] <path>...]
+'git log' [<options>] [<revision range>] [[\--] <path>...]
@@ -62,12 +62,14 @@ produced by --stat etc.
        Note that only message is considered, if also a diff is shown
        its size is not included.
-       Show only commits between the named two commits.  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].
+<revision range>::
+       Show only commits in the specified revision range.  When no
+       <revision range> is specified, it defaults to 'HEAD' (ie. the
+       whole history leading to the current commit).  master..HEAD
+       specifies all the commits reachable from 'HEAD', but not from
+       'master'. For a complete list of ways to spell
+       <revision range>, see the "Specifying Ranges" section of
+       linkgit:gitrevisions[7].
 [\--] <path>...::
        Show only commits that are enough to explain how the files

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

Reply via email to