]>
Commit | Line | Data |
---|---|---|
1ed6f2c5 | 1 | gitrevisions(7) |
142d035a | 2 | =============== |
1ed6f2c5 MG |
3 | |
4 | NAME | |
5 | ---- | |
2de9b711 | 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 | |
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 |