blob: d407b7dee127b10a82c2b8e5101b44ce6996a24e [file] [log] [blame]
Michael J Gruber1ed6f2c2010-07-05 18:11:40 +02001gitrevisions(7)
Junio C Hamano142d0352015-10-22 10:09:07 -07002===============
Michael J Gruber1ed6f2c2010-07-05 18:11:40 +02003
4NAME
5----
Nguyễn Thái Ngọc Duy1b81d8c2018-05-20 20:40:02 +02006gitrevisions - Specifying revisions and ranges for Git
Michael J Gruber1ed6f2c2010-07-05 18:11:40 +02007
8SYNOPSIS
9--------
10gitrevisions
11
12
13DESCRIPTION
14-----------
15
16Many Git commands take revision parameters as arguments. Depending on
17the command, they denote a specific commit or, for commands which
Philip Oakley6cb4f782016-08-12 08:07:44 +010018walk the revision graph (such as linkgit:git-log[1]), all commits which are
Philip Oakley8cf57392016-08-12 08:07:45 +010019reachable from that commit. For commands that walk the revision graph one can
20also specify a range of revisions explicitly.
Michael J Gruber1ed6f2c2010-07-05 18:11:40 +020021
Ævar Arnfjörð Bjarmasonfe802bd2018-08-31 20:10:02 +000022In addition, some Git commands (such as linkgit:git-show[1] and
23linkgit:git-push[1]) can also take revision parameters which denote
24other objects than commits, e.g. blobs ("files") or trees
25("directories of files").
Michael J Gruber1ed6f2c2010-07-05 18:11:40 +020026
27include::revisions.txt[]
28
29
30SEE ALSO
31--------
32linkgit:git-rev-parse[1]
33
34GIT
35---
36Part of the linkgit:git[1] suite