Re: [RFC] Using gitrevisions :/search style with other operators
- From
- Yann Dirson <dirson@bertin.fr>
- Date
- Nov 10, 2010, 07:46 UTC
- Message-ID
- <20101110084609.78f532a5@chalon.bertin.fr>
- In-Reply-To
- <23523534-F7A7-4D61-A899-8B3B28566EA7@sb.org>
On Tue, 09 Nov 2010 23:46:59 -0800 Kevin Ballard <kevin@sb.org> wrote:
Show 15 quoted lines
> On Nov 9, 2010, at 11:32 PM, Yann Dirson wrote:
>
> >> Another thing to consider - the current :/foo syntax searches for
> >> the newest commit reachable from any ref. Using the ^{} syntax will
> >> require specifying a ref first. I'm not sure this is a problem
> >> though, as I'm not really sure why :/foo searches from all refs to
> >> begin with.
> >
> > The syntax could be extended so that ^{whatever} starts looking at
> > current commit (ie. HEAD), somewhat like @{whatever} looks at
> > reflog for current branch.
>
> :/foo doesn't start from the current commit - it searches all refs.
> However, making ^{} search all refs if not given one doesn't make
> sense for any operator except :/foo, so I don't think it's worth doingYes, that's why I suggested to make it search from HEAD, not from all refs.
-- Yann Dirson - Bertin Technologies