On Mon, Mar 2, 2009 at 5:39 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > I personally do not think that makes much sense (and I find ** ugly, too). > > We traditionally supported '*' only at the end, and it always has meant > "match through the end, including slashes". Oh, good point, I had not thought that through very well. > Requiring 'match including slashes' to be spelled as '**' only when it is > not at the end is unnecessarily confusing. > > Is there a valid use case when * wants to match across directory > boundaries when it is not at the end? I offhand do not think of a sane > one. > > So, it might make it easiest to understand if we say * usually does not > match slash, except when it is used at the end immediately after a slash, > in which case it means "match through the end". That seems simple enough. j. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
