Re: [PATCH 0/5] extend git-describe pattern matching
- From
Jacob Keller <jacob.keller@gmail.com>
- Date
- Jan 13, 2017, 20:41 UTC
- Message-ID
- <CA+P7+xoR7oOEg-WW4AqWNYfn4f2W4vwxFLyxc+buzAi7h2xfyw@mail.gmail.com>
- In-Reply-To
- <xmqqpojqhk3i.fsf@gitster.mtv.corp.google.com>
On Fri, Jan 13, 2017 at 10:48 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 12 quoted lines
> Jacob Keller <jacob.e.keller@intel.com> writes: > >> From: Jacob Keller <jacob.keller@gmail.com> >> >> Teach git describe and git name-rev the ability to match multiple >> patterns inclusively. Additionally, teach these commands to also accept >> negative patterns to discard any refs which match. > > You made quick responses to reviews with "will change", so I am not > queuing this round to my tree; please don't mistake that as my > indifference or opposition to the topic. This sounds like a good > thing.
Perfect. I will probably take a few days till I am back at a computer and can do this, but I will be submitting with the suggested changes soon.
Show 8 quoted lines
> > As to the semantics of mixing positives and negatives, I would > recommend this to follow how positive and negative pathspecs mix. > IIRC we chose to use the most simple and easy to explain option, > i.e. a thing must match at least one of the positives and must not > match any of the negatives to be considered a match. > >
That is the current implementation, so I will stick with it. It's the simplest, and easiest to implement.
Thanks, Jake