From: Jeff King <peff@peff.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFD} Use regex's in :/ revision naming machinery
Date: Tue, 6 Apr 2010 00:31:34 -0400 [thread overview]
Message-ID: <20100406043133.GA3901@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1004051551180.21411@i5.linux-foundation.org>
On Mon, Apr 05, 2010 at 04:00:59PM -0700, Linus Torvalds wrote:
> So this is very much debatable, but I'm including a patch for the
> discussion to start.
FWIW, this came up quite a while ago and people generally seemed to
think it was a good idea, but the patch from Dscho (cc'd) never made it
upstream.
The old thread is here:
http://article.gmane.org/gmane.comp.version-control.git/50010
Personally, I think regex matching makes :/ a bit more usable, though
since that thread I have found I don't use :/ all that often (instead
needing to pick through the results of --grep looking for the commit in
question, at which point I just cut-and-paste the commit sha1). I agree
as was suggested elsewhere in the thread that searching from HEAD would
help.
-Peff
next prev parent reply other threads:[~2010-04-06 4:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 23:00 [RFD} Use regex's in :/ revision naming machinery Linus Torvalds
2010-04-06 1:51 ` Junio C Hamano
2010-04-06 2:08 ` Junio C Hamano
2010-04-06 2:15 ` Linus Torvalds
2010-04-06 4:31 ` Jeff King [this message]
2010-04-06 7:55 ` Johannes Sixt
2010-04-06 14:19 ` Linus Torvalds
2010-04-07 1:04 ` Nazri Ramliy
-- strict thread matches above, loose matches on Subject: below --
2010-04-06 7:02 Yann Dirson
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=20100406043133.GA3901@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.org \
/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).