Re: [PATCH] object name: introduce ':::<oneline prefix>' notation
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 24, 2007, 01:35 UTC
- Message-ID
- <Pine.LNX.4.63.0702240229540.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <7vzm741hfx.fsf@assigned-by-dhcp.cox.net>
Hi,
On Fri, 23 Feb 2007, Junio C Hamano wrote:
Show 15 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Fri, 23 Feb 2007, Johannes Schindelin wrote:
> >
> >> To name a commit, you can now say
> >>
> >> git rev-parse ':::Initial revision of "git"'
> >
> > Alex Riesen and Shawn Pearce suggested ":/" instead of ":::", to reflect
> > the searching nature ("/" is the key to search in "less" output).
> >
> > Comments?
>
> Sounds good. "git show :/path" does not currently mean "find /path in
> the index", so I do not see offhand it would interfere with anything.That's also what Shawn said.
Show 6 quoted lines
> However, it would be worthwhile to plant an escape hatch for future > extension. Using short-and-sweet ":/" for the most common case such as > exact prefix match would be fine, but we might want to say: > > ':/!' syntax is reserved for future extension and does > not look for a string that begins with "!".
Okay. Will rework.
Show 10 quoted lines
> Obvious extension possibilities include: > > ":/!(r=regexp)" > ":/!(a=author)" > ":/!(d=2001-09-17)" > ":/!(p=Documentation/)" > > or various combination of them e.g. > > ":!(p=Documentation/)!(a=Johannes)Update command list"
They are much harder to implement. So I'll leave that to others :-)
> By the way, where do you start digging from? From all refs?
Yes, all refs. In order of the date.
Ciao, Dscho