Skip to content

Commit a0d2ceb

Browse files
peffgitster
authored andcommitted
doc/rev-parse: clarify reflog vs --until for specifying revisions
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>
1 parent 7829f20 commit a0d2ceb

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

Documentation/git-rev-parse.txt

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,10 @@ blobs contained in a commit.
184184
second ago\}' or '\{1979-02-26 18:30:00\}') to specify the value
185185
of the ref at a prior point in time. This suffix may only be
186186
used immediately following a ref name and the ref must have an
187-
existing log ($GIT_DIR/logs/<ref>).
187+
existing log ($GIT_DIR/logs/<ref>). Note that this looks up the state
188+
of your *local* ref at a given time; e.g., what was in your local
189+
`master` branch last week. If you want to look at commits made during
190+
certain times, see `--since` and `--until`.
188191

189192
* A ref followed by the suffix '@' with an ordinal specification
190193
enclosed in a brace pair (e.g. '\{1\}', '\{15\}') to specify

0 commit comments

Comments
 (0)