summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2008-06-30 00:44:19 -0700
committerJunio C Hamano <gitster@pobox.com>2008-06-30 00:44:19 -0700
commit66037991d3fd2ac7e699c7bd21d939b9e397f6a4 (patch)
tree1de603939614374c990c78cb15620f10b8e83c52
parentf9d800e2074a60a009e7c670e396a379d8c46cc5 (diff)
parenta0d2ceb2769731571cdd195582bfedf90225e712 (diff)
downloadgit-66037991d3fd2ac7e699c7bd21d939b9e397f6a4.tar.gz
Merge branch 'maint'
* maint: doc/rev-parse: clarify reflog vs --until for specifying revisions
-rw-r--r--Documentation/git-rev-parse.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 9e273bc5a6..59e95adf42 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -184,7 +184,10 @@ blobs contained in a commit.
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
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
enclosed in a brace pair (e.g. '\{1\}', '\{15\}') to specify