Re: [PATCH 0/2] [RFD] Using gitrevisions :/search style with other operators
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Dec 9, 2010, 00:30 UTC
- Message-ID
- <AANLkTi=AyCxn=dcKQQmT0_6Oc36AX6XDA4Dhhk7WLSN0@mail.gmail.com>
- In-Reply-To
- <201012082047.44022.jnareb@gmail.com>
2010/12/9 Jakub Narebski <jnareb@gmail.com>:
> I wonder if it would be possible to make :/<regex> (which looks a bit
> like searching the index) to be an alias to --all^{/<regex>}...It looks a bit strange to my eyes to merge normal option name with revision syntax. But I think it's possible. Do we allow branch/tag name with leading '-'?
> Or if we can make ^{/<regex>} to act on revision range specified by
> earlier commits, so for example foo..bar^{/<regex>} would work.There is another case: branch/tag selection. Instead of looking in all refs, people may want to look only in nd/* branches. My branches are almost flat, so I don't find any use. But someone might. And we can solve the "all branches" case above with simply "*". The exact syntax, I don't know.
> As to :/!<regexp> form: isn't it reserved for non-match?
It is reserved and not attached with any meaning.
> Thank you for working on this.
You're welcome. I needed to look for my branches in pu and was tired of copy/paste.
-- Duy