Re: RFC: git bisect should accept "paths-to-be-excluded"

From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date: Sep 17, 2013, 18:12 UTC
Message-ID: <1496b663-6b6c-45a2-95d1-cbe634b0d160@email.android.com>
In-Reply-To: <xmqqsix3z8ie.fsf@gitster.dls.corp.google.com>

Junio C Hamano <gitster@pobox.com> napisał:

Show 12 quoted lines

>Yeah, it is easy to say that
>
>	git log -- A ':(exclude)A/B' A/B/C
>
>has two positive (A, A/B/C) and one negative (A/B), and then the
>most specific one A/B/C matches a path A/B/C/D and hence A/B/C/D is
>included.
>
>But to actually _design_ it, there are ambiguities that makes
>understanding and explaining the semantics, especially given
>pathspecs can have wildcards, icase matches, etc.  For example, is
>":(exclude,icase)A/B/?"  more specific than "A/?/C" or less?

 What about simply iterating over options in order in which they are specified and the last option that matches specifies the result?

-- 
Piotr Krukowiecki