Browse Source
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>maint
Michael J Gruber
15 years ago
committed by
Junio C Hamano
2 changed files with 36 additions and 1 deletions
@ -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 |
Loading…
Reference in new issue