Re: [PATCH] attr: allow pattern escape using backslashes

From: Duy Nguyen <pclouds@gmail.com>
Date: Feb 27, 2013, 12:23 UTC
Message-ID: <CACsJy8Ag8rJ4P6w6ZCB0vBp6Hzqr_G5vWS_Jt=RNQT8+hF_w_A@mail.gmail.com>
In-Reply-To: <7v7gly5az0.fsf@alter.siamese.dyndns.org>

On Sun, Feb 24, 2013 at 4:15 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 7 quoted lines

> Speaking of .gitignore, I recall that there was a hanging discussion
> on allowing a pattern to name the directory that the .gitignore file
> appears in, which I do not think we currently support.  With such a
> feature, instead of listing "/junk" in the .gitignore file at the
> top-level to say that everything inside the "junk" directory is
> ignored by default, we could instead say "<this>" at the beginning
> of the .gitignore file in the "junk" directory.

Shouldn't "/" alone in junk/.gitignore express that? It does not work, but I think it's a natural interpretation of the syntax.

Show 6 quoted lines

> I think "* <attr>"
> in the .gitattributes file in a directory causes "git check-attr ."
> in that directory to report the <attr>, and we may want to have some
> way to allow "git check-ignore ." to be affected by the .gitignore
> file in the same directory in a similar way, but I do not have a
> very strong opinion.  Do people have any comment on this?

-- 
Duy