On Tue, Sep 17, 2013 at 9:04 PM, Junio C Hamano <gits...@pobox.com> wrote:
> Piotr Krukowiecki <piotr.krukowie...@gmail.com> writes:
>> What about simply iterating over options in order in which they
>> are specified and the last option that matches specifies the
> 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.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html