git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] ref-log: allow ref@{count} syntax.

From
Shawn Pearce <spearce@spearce.org>
Date
Oct 6, 2006, 16:05 UTC
Message-ID
<20061006160521.GA20024@spearce.org>
In-Reply-To
<7vsli20y1c.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 13 quoted lines
> 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>
> ---
> 
>  * The implementation is rather hacky but I think this is
>    mildly useful.  Likes, dislikes?
Ack'd.

Its a useful feature. Something I've been wanting myself for some time. I usually just guess with '@{5.minutes.ago}' or some nonsense until I find the right time. But since I know it was X operations ago, '@{X}' will be very handy. Thanks!

-- 
Shawn.
Previous: Junio C Hamano
Message 2 of 2 in “ref-log: allow ref@{count} syntax.”
  1. ref-log: allow ref@{count} syntax.Junio C Hamano, Oct 6, 2006
  2. Shawn PearceOct 6, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.