From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] ref-log: allow ref@{count} syntax.
Date: Fri, 6 Oct 2006 12:05:21 -0400 [thread overview]
Message-ID: <20061006160521.GA20024@spearce.org> (raw)
In-Reply-To: <7vsli20y1c.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> 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.
prev parent reply other threads:[~2006-10-06 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 6:16 [PATCH] ref-log: allow ref@{count} syntax Junio C Hamano
2006-10-06 16:05 ` Shawn Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061006160521.GA20024@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).