Junio C Hamano <gits...@pobox.com> napisał: >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 -- 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
