Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] object name: introduce ':::<oneline prefix>' notation
Date: Fri, 23 Feb 2007 20:30:15 -0500	[thread overview]
Message-ID: <20070224013015.GA9021@coredump.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0702240220300.22628@wbgn013.biozentrum.uni-wuerzburg.de>

I said:

> > > Alex Riesen and Shawn Pearce suggested ":/" instead of ":::", to 
> > argument? Why not just add a '--grep' or similar option to indicate that 

Hmm, I completely misread your patch comments in the first place, so
forget my suggestion; it obviously needs to be a per-committish
indicator, not a per-command flag.

I think :/ is slightly easier on the eyes than :::. Plus it opens the
door for :? to find the oldest such match (though I'm not sure if it
would be by topology or date).

Of course it's starting to look a bit like line noise...maybe we just
need :-/ and :-).

-Peff

  reply	other threads:[~2007-02-24  1:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 18:32 [PATCH] object name: introduce ':::<oneline prefix>' notation Johannes Schindelin
2007-02-23 22:48 ` Johannes Schindelin
2007-02-24  1:12   ` Jeff King
2007-02-24  1:21     ` Johannes Schindelin
2007-02-24  1:30       ` Jeff King [this message]
2007-02-24  1:49         ` Johannes Schindelin
2007-02-24  1:57           ` Jeff King
2007-02-24  2:14             ` Johannes Schindelin
2007-02-24  2:15               ` Jeff King
2007-02-24  1:53         ` Nicolas Pitre
2007-02-24  1:18   ` Junio C Hamano
2007-02-24  1:35     ` Johannes Schindelin
2007-02-24  1:46       ` Junio C Hamano
2007-02-24  1:56         ` Nicolas Pitre
2007-02-24  2:10           ` Johannes Schindelin

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=20070224013015.GA9021@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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