From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 27 Feb 2013 15:42:20 GMT
Subject: Re: [PATCH] attr: allow pattern escape using backslashes
Message-ID: <7vlia9kbkz.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CACsJy8Ag8rJ4P6w6ZCB0vBp6Hzqr_G5vWS_Jt=RNQT8+hF_w_A@mail.gmail.com>

Duy Nguyen <pclouds@gmail.com> writes:

> On Sun, Feb 24, 2013 at 4:15 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> 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.

Yup, there is nothing that you can plug to the "<this>" in the above
to make it mean "junk" directory is ignored.  A trailing "/" is
removed after noting the fact that the entry is about a directory
and leaves an empty string, and it would be OK to define that an
empty string matches the directory the gitignore file appears in.