undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc/rev-parse: clarify reflog vs --until for specifying revisions

Browse Source 
The rev-parse manpage introduces the branch@{date} syntax,
and mentions the reflog specifically. However, new users may
not be familiar with the distinction between the reflog and
the commit date, so let's help them out with a "you may be
interested in --until" pointer.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Jeff King 2008-06-29 23:27:45 -04:00 committed by Junio C Hamano
parent 7829f20f5b
commit a0d2ceb276
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/git-rev-parse.txt
View File

@ -184,7 +184,10 @@ blobs contained in a commit.
second ago\}' or '\{1979-02-26 18:30:00\}') to specify the value second ago\}' or '\{1979-02-26 18:30:00\}') to specify the value
of the ref at a prior point in time. This suffix may only be of the ref at a prior point in time. This suffix may only be
used immediately following a ref name and the ref must have an used immediately following a ref name and the ref must have an
existing log ($GIT_DIR/logs/<ref>). existing log ($GIT_DIR/logs/<ref>). Note that this looks up the state
of your *local* ref at a given time; e.g., what was in your local
`master` branch last week. If you want to look at commits made during
certain times, see `--since` and `--until`.
* A ref followed by the suffix '@' with an ordinal specification * A ref followed by the suffix '@' with an ordinal specification
enclosed in a brace pair (e.g. '\{1\}', '\{15\}') to specify enclosed in a brace pair (e.g. '\{1\}', '\{15\}') to specify