From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date: Tue, 17 Sep 2013 19:41:50 GMT
Subject: Re: RFC: git bisect should accept "paths-to-be-excluded"
Message-ID: <CAA01Csp6tjKJ9LqX+9qcJL4t3kfFJCagjZQ=QwddvscPori9Ow@mail.gmail.com>
In-Reply-To: <xmqqpps7xoax.fsf@gitster.dls.corp.google.com>

On Tue, Sep 17, 2013 at 9:04 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
>
>>  What about simply iterating over options in order in which they
>>  are specified and the last option that matches specifies the
>>  result?
>
> But isn't it very inconsistent from the way normal pathspec works?
> "git log -- A B" and "git log -- B A" would give the same result.

Both are include-type filters. "--include A --include B" will give the
same result as "--include B --include A" too.

Are there existing include/exclude filters where order does not
matter? For example gitattributes(5) says "When more than one pattern
matches the path, a later line overrides an earlier line."

Ignoring (possible) inconsistency thing, I think they are easy to
understand and use.


-- 
Piotr Krukowiecki