Update the documentation for the new '@{...}' syntax
Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net>
Johannes Schindelin committed
Feb 2, 2007 at 00:21 UTC
1e5db3075ae1f22cbffc273321e94b60d5f23927
1 file changed
+4
Documentation/git-rev-parse.txt
+4
@@ -160,6 +160,10 @@ blobs contained in a commit.
160
immediately following a ref name and the ref must have an existing
161
log ($GIT_DIR/logs/<ref>).
162
163
+* You can use the '@' construct with an empty ref part to get at a
164
+ reflog of the current branch. For example, if you are on the
165
+ branch 'blabla', then '@\{1\}' means the same as 'blabla@\{1\}'.
166
+
167
* A suffix '{caret}' to a revision parameter means the first parent of
168
that commit object. '{caret}<n>' means the <n>th parent (i.e.
169
'rev{caret}'