projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 422b4a0) | patch
ref-log: allow ref@{count} syntax.
authorJunio C Hamano <junkio@cox.net>
Fri, 6 Oct 2006 06:16:15 +0000 (23:16 -0700)
committerJunio C Hamano <junkio@cox.net>
Fri, 6 Oct 2006 06:17:11 +0000 (23:17 -0700)
commitab2a1a32ffa5a39aaf4204bd717562bce49e0a36
tree21b6b7f63d6e74f023df5d338282b0a75df55c35tree | snapshot
parent422b4a0e03658d0933a7abc149f175735ea9c4b5commit | diff
ref-log: allow ref@{count} syntax.

Often I find myself wanting to say 'tip of "next" before I
merged the last three topics'.  Now I can say that with:

git log next@{3}..next

Since small integers alone are invalid input strings to
approxidate, there is no fear of confusion.

Signed-off-by: Junio C Hamano <junkio@cox.net>
refs.c diff | blob | blame | history
refs.h diff | blob | blame | history
sha1_name.c diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.