Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Update the documentation for the new '@{...}' syntax
author
Johannes Schindelin
<Johannes.Schindelin@gmx.de>
Thu, 1 Feb 2007 23:21:49 +0000
(
00:21
+0100)
committer
Junio C Hamano
<junkio@cox.net>
Fri, 2 Feb 2007 05:50:46 +0000
(21:50 -0800)
Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-rev-parse.txt
patch
|
blob
|
history
raw
|
patch
| inline |
side by side
(parent:
d271fd5
)
diff --git
a/Documentation/git-rev-parse.txt
b/Documentation/git-rev-parse.txt
index aeb37b65d26dbc2873438bd7b2c36bf89d24b056..4041a1607081ee6e8d93065c67fc72a513c20b17 100644
(file)
--- a/
Documentation/git-rev-parse.txt
+++ b/
Documentation/git-rev-parse.txt
@@
-160,6
+160,10
@@
blobs contained in a commit.
immediately following a ref name and the ref must have an existing
log ($GIT_DIR/logs/<ref>).
+* You can use the '@' construct with an empty ref part to get at a
+ reflog of the current branch. For example, if you are on the
+ branch 'blabla', then '@\{1\}' means the same as 'blabla@\{1\}'.
+
* A suffix '{caret}' to a revision parameter means the first parent of
that commit object. '{caret}<n>' means the <n>th parent (i.e.
'rev{caret}'