summaryrefslogtreecommitdiff
path: root/Documentation/git-log.txt
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2007-01-17 21:08:09 -0500
committerJunio C Hamano <junkio@cox.net>2007-01-17 20:45:41 -0800
commit41a5564e054043945e365c580abab724e12744ff (patch)
tree024d969caa86b4a7711c993b399315d9be83847c /Documentation/git-log.txt
parentee53aff486d380986e549ea93a5d68e7b7607293 (diff)
downloadgit-41a5564e054043945e365c580abab724e12744ff.tar.gz
Refer users to git-rev-parse for revision specification syntax.
The revision specification syntax (sometimes referred to as SHA1-expressions) is accepted almost everywhere in Git by almost every tool. Unfortunately it is only documented in git-rev-parse.txt, and most users don't know to look there. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-log.txt')
-rw-r--r--Documentation/git-log.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 60610f91f4..b8029463d9 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -34,6 +34,9 @@ include::pretty-formats.txt[]
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 "SPECIFYING REVISIONS" section in
+ gitlink:git-rev-parse[1].
-p::
Show the change the commit introduces in a patch form.