Documentation: gitrevisions
Create a new man page gitrevisions(7) which contains the revsions and ranges documentation but not more. This uses (per include) the same bits as the pertaining section of git-rev-parse(1). Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Michael J Gruber committed
Jul 5, 2010 at 18:11 UTC
1ed6f2c5b97de939e2f52da6a60785f3d9a3de86
2 files changed
+36
-1
Documentation/Makefile
+1
-1
@@ -6,7 +6,7 @@ MAN5_TXT=gitattributes.txt gitignore.txt gitmodules.txt githooks.txt \
6
gitrepository-layout.txt
7
MAN7_TXT=gitcli.txt gittutorial.txt gittutorial-2.txt \
8
gitcvs-migration.txt gitcore-tutorial.txt gitglossary.txt \
9
- gitdiffcore.txt gitworkflows.txt
9
+ gitdiffcore.txt gitrevisions.txt gitworkflows.txt
10
11
MAN_TXT = $(MAN1_TXT) $(MAN5_TXT) $(MAN7_TXT)
12
MAN_XML=$(patsubst %.txt,%.xml,$(MAN_TXT))
Documentation/gitrevisions.txt
new
+35
@@ -0,0 +1,35 @@
1
+gitrevisions(7)
2
+================
3
+
4
+NAME
5
+----
6
+gitrevisions - specifying revisions and ranges for git
7
+
8
+SYNOPSIS
9
+--------
10
+gitrevisions
11
+
12
+
13
+DESCRIPTION
14
+-----------
15
+
16
+Many Git commands take revision parameters as arguments. Depending on
17
+the command, they denote a specific commit or, for commands which
18
+walk the revision graph (such as linkgit:git-log[1]), all commits which can
19
+be reached from that commit. In the latter case one can also specify a
20
+range of revisions explicitly.
21
+
22
+In addition, some Git commands (such as linkgit:git-show[1]) also take
23
+revision parameters which denote other objects than commits, e.g. blobs
24
+("files") or trees ("directories of files").
25
+
26
+include::revisions.txt[]
27
+
28
+
29
+SEE ALSO
30
+--------
31
+linkgit:git-rev-parse[1]
32
+
33
+GIT
34
+---
35
+Part of the linkgit:git[1] suite