Re: .gitattributes override behavior (possible bug, or documentation bug)

From: Dakota Hawkins <dakota@dakotahawkins.com>
Date: Mar 20, 2018, 03:40 UTC
Message-ID: <CAHnyXxRjqKKyp0U7ryxUk4BMHGdqN1pMYC66BDG+8UYPaF7a3w@mail.gmail.com>
In-Reply-To: <xmqq8tanto90.fsf@gitster-ct.c.googlers.com>

On Mon, Mar 19, 2018 at 11:33 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 18 quoted lines

> Jeff King <peff@peff.net> writes:
>
>> The best you can probably do is:
>>
>>   /.readme-docs/* diff=foo
>>
>> Since you have no diff.foo.* config, that will behave in the default way
>> (including respecting the usual "is it binary" checks). So a bit hacky,
>> but I think it would work as "ignore prior diff".
>
> You can say
>
>         /.readme-docs/* !diff
>
> I think.  Thre is a difference between setting it to "false"
> (i.e. Unset) and reverting it to unspecified state.
>
> Isn't that what you want here?

In this case, I think so? In this context I don't necessarily know the files in /.readme-docs/ are binary (though that's its intent). Ideally, I just want it to do whatever it did before the match gave it "diff=lfs". I realize that that's not possible/feasible, so I asked in a separate reply whether it might be a good idea to ask git-lfs for a "no-lfs" filter for exactly this situation.

The actual "lfs" section of my .gitattributes file is about 65 lines for 65 different extensions, so I'd prefer to handle the exclusion of a directory without having to repeat that whole block with different options, if that makes sense :)