Re: Change on check-attr behavior

From: Jeff King <peff@peff.net>
Date: Jan 17, 2019, 16:07 UTC
Message-ID: <20190117160752.GA29375@sigill.intra.peff.net>
In-Reply-To: <CAK3b1G+88a=xfO=6wfRi1SMy3xtca2NcFyxuBLKwSifb_L9xwA@mail.gmail.com>

On Thu, Jan 17, 2019 at 03:47:09PM +0000, Sérgio Peixoto wrote:

Show 26 quoted lines

> I think there is a bug on the check-attr behavior of git when asking
> for the "allowed-ext" attribute.  Check the logs below to see that
> with version  2.20.1.windows.1 we get unspecified even the attribute
> is there as you can see when asking for all the attributes.
> 
> === OLD VERSION ===
> > git version
> git version 2.8.1.windows.1
> 
> > git check-attr -a test.py
> test.py: text: set
> test.py: allowed-ext: 100
> 
> > git check-attr allowed-ext test.py
> test.py: allowed-ext: 100
> 
> === NEW VERSION ===
> > git --version
> git version 2.20.1.windows.1
> 
> > git check-attr -a test.py
> test.py: text: set
> test.py: allowed-ext: 100
> 
> > git check-attr allowed-ext test.py
> test.py: allowed-ext: unspecified

I can't reproduce here (on Linux, but I don't think the attr code is particularly Windows-specific). Can you show us what's in your .gitattributes file(s)?

-Peff