mirror of
https://github.com/git/git.git
synced 2026-10-31 21:15:39 +01:00
Julia EvansandTuomas Ahola
fbbc33935a
Remove the SYNOPSIS section from the section 7 man pages where appropriate, to avoid having a section that contains no information. It's not the norm in section 7 to always require a SYNOPSIS. Update the perl script with a special case for section 7. Tested by running `make lint-docs`, and looked at the renaming synopses with this fish script snippet: for i in *.7 echo $i; grep SYNOPSIS -A 5 (string replace .7 .adoc $i) end Co-authored-by: Tuomas Ahola <taahol@utu.fi> Signed-off-by: Tuomas Ahola <taahol@utu.fi> Signed-off-by: Julia Evans <julia@jvns.ca> Signed-off-by: Junio C Hamano <gitster@pobox.com>
32 lines
791 B
Plaintext
32 lines
791 B
Plaintext
gitrevisions(7)
|
|
===============
|
|
|
|
NAME
|
|
----
|
|
gitrevisions - Specifying revisions and ranges for Git
|
|
|
|
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 are
|
|
reachable from that commit. For commands that walk the revision graph one can
|
|
also specify a range of revisions explicitly.
|
|
|
|
In addition, some Git commands (such as linkgit:git-show[1] and
|
|
linkgit:git-push[1]) can also take revision parameters which denote
|
|
other objects than commits, e.g. blobs ("files") or trees
|
|
("directories of files").
|
|
|
|
include::revisions.adoc[]
|
|
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkgit:git-rev-parse[1]
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|