Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
doc: gitrevisions - clarify 'latter case' is revision walk
author
Philip Oakley
<philipoakley@iee.org>
Fri, 12 Aug 2016 07:07:45 +0000
(08:07 +0100)
committer
Junio C Hamano
<gitster@pobox.com>
Sun, 14 Aug 2016 02:36:44 +0000
(19:36 -0700)
The prior sentence has too many clauses for easy parsing.
Replace 'the latter case' with a direct quote.
Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/gitrevisions.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
6cb4f78
)
diff --git
a/Documentation/gitrevisions.txt
b/Documentation/gitrevisions.txt
index 33039c6228d76428eac0d9b16bde5c6f42612f8d..27dec5b91d08bbdb114400dd3c86a8cf515e8774 100644
(file)
--- a/
Documentation/gitrevisions.txt
+++ b/
Documentation/gitrevisions.txt
@@
-16,8
+16,8
@@
DESCRIPTION
Many Git commands take revision parameters as arguments. Depending on
the command, they denote a specific commit or, for commands which
walk the revision graph (such as linkgit:git-log[1]), all commits which are
Many Git commands take revision parameters as arguments. Depending on
the command, they denote a specific commit or, for commands which
walk the revision graph (such as linkgit:git-log[1]), all commits which are
-reachable from that commit.
In the latter case one can also specify a
-range of revisions explicitly.
+reachable from that commit.
For commands that walk the revision graph one can
+
also specify a
range of revisions explicitly.
In addition, some Git commands (such as linkgit:git-show[1]) also take
revision parameters which denote other objects than commits, e.g. blobs
In addition, some Git commands (such as linkgit:git-show[1]) also take
revision parameters which denote other objects than commits, e.g. blobs