summaryrefslogtreecommitdiffstats
path: root/gitrevisions.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@kernel.org>2010-07-15 22:24:45 +0000
committerJunio C Hamano <junio@kernel.org>2010-07-15 22:24:45 +0000
commit78e3a7820b2267111cd2f29fd3d06e8919f2b36c (patch)
treee5eb61d417f8655688f52d01beeddb01b9503560 /gitrevisions.txt
parent635553978d5d3414c3d9699aa009ae29839356ab (diff)
downloadgit-htmldocs-78e3a7820b2267111cd2f29fd3d06e8919f2b36c.tar.gz
Autogenerated HTML docs for v1.7.2-rc3-39-g53b30
Diffstat (limited to 'gitrevisions.txt')
-rw-r--r--gitrevisions.txt35
1 files changed, 35 insertions, 0 deletions
diff --git a/gitrevisions.txt b/gitrevisions.txt
new file mode 100644
index 000000000..fc4789f98
--- /dev/null
+++ b/gitrevisions.txt
@@ -0,0 +1,35 @@
+gitrevisions(7)
+================
+
+NAME
+----
+gitrevisions - specifying revisions and ranges for git
+
+SYNOPSIS
+--------
+gitrevisions
+
+
+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 can
+be reached from that commit. In the latter case 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
+("files") or trees ("directories of files").
+
+include::revisions.txt[]
+
+
+SEE ALSO
+--------
+linkgit:git-rev-parse[1]
+
+GIT
+---
+Part of the linkgit:git[1] suite