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>

Jeff King committed Jun 29, 2008 at 23:27 UTC a0d2ceb2769731571cdd195582bfedf90225e712

1 file changed +4 -1

Documentation/git-rev-parse.txt

+4 -1

@@ -184,7 +184,10 @@ blobs contained in a commit.

184 second ago\}' or '\{1979-02-26 18:30:00\}') to specify the value

185 of the ref at a prior point in time. This suffix may only be

186 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`.

191

192 * A ref followed by the suffix '@' with an ordinal specification

193 enclosed in a brace pair (e.g. '\{1\}', '\{15\}') to specify