| Junio C Hamano | 78e3a78 | 2010-07-15 22:24:45 | [diff] [blame] | 1 | gitrevisions(7) |
| Junio C Hamano | ee61580 | 2015-10-29 21:45:26 | [diff] [blame] | 2 | =============== |
| Junio C Hamano | 78e3a78 | 2010-07-15 22:24:45 | [diff] [blame] | 3 | |
| 4 | NAME |
| 5 | ---- |
| Junio C Hamano | 076ffcc | 2013-02-06 05:13:21 | [diff] [blame] | 6 | gitrevisions - specifying revisions and ranges for Git |
| Junio C Hamano | 78e3a78 | 2010-07-15 22:24:45 | [diff] [blame] | 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 |
| Junio C Hamano | cd45166 | 2016-09-13 00:54:09 | [diff] [blame] | 18 | walk the revision graph (such as linkgit:git-log[1]), all commits which are |
| 19 | reachable from that commit. For commands that walk the revision graph one can |
| 20 | also specify a range of revisions explicitly. |
| Junio C Hamano | 78e3a78 | 2010-07-15 22:24:45 | [diff] [blame] | 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 |
