]>
Commit | Line | Data |
---|---|---|
1ed6f2c5 | 1 | gitrevisions(7) |
142d035a | 2 | =============== |
1ed6f2c5 MG |
3 | |
4 | NAME | |
5 | ---- | |
1b81d8cb | 6 | gitrevisions - Specifying revisions and ranges for Git |
1ed6f2c5 MG |
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 | |
6cb4f785 | 18 | walk the revision graph (such as linkgit:git-log[1]), all commits which are |
8cf57394 PO |
19 | reachable from that commit. For commands that walk the revision graph one can |
20 | also specify a range of revisions explicitly. | |
1ed6f2c5 | 21 | |
fe802bd2 ÆAB |
22 | In addition, some Git commands (such as linkgit:git-show[1] and |
23 | linkgit:git-push[1]) can also take revision parameters which denote | |
24 | other objects than commits, e.g. blobs ("files") or trees | |
25 | ("directories of files"). | |
1ed6f2c5 MG |
26 | |
27 | include::revisions.txt[] | |
28 | ||
29 | ||
30 | SEE ALSO | |
31 | -------- | |
32 | linkgit:git-rev-parse[1] | |
33 | ||
34 | GIT | |
35 | --- | |
36 | Part of the linkgit:git[1] suite |