From: Nguyen Thai Ngoc Duy Date: Tue, 01 Feb 2011 14:56:06 GMT Subject: Re: [1.8.0] Unify "pathspec" semantics Message-ID: In-Reply-To: <7voc6x57el.fsf_-_@alter.siamese.dyndns.org> On Tue, Feb 1, 2011 at 12:07 AM, Junio C Hamano wrote: > Some projects may track a file whose name is asterisk (e.g. "foo/*") and > output from "git log 'foo/*'" would look different.  Before the change, > only commits that touch that exact path would be shown, but after the > change, any commit that touch a path underneath "foo/" directory will be > shown.  This is a backward incompatible change. Can we support quoting wildcards? I can imagine a file name such as '***DO NOT DO IT***'. People who wish to match exactly that file would have hard time ahead without a way to tell git those stars are literal. A prefix/special leading symbol or cmdline option to indicate the given pathspec is literal is fine too (e.g "!literal:***hey***" or --literal "***hey***"). In fact I can extend that to support negative pathspecs. -- Duy