git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Change on check-attr behavior

From
SPSérgio Peixoto <sergio.peixoto@gmail.com>
Date
Jan 17, 2019, 15:47 UTC
Message-ID
<CAK3b1G+88a=xfO=6wfRi1SMy3xtca2NcFyxuBLKwSifb_L9xwA@mail.gmail.com>
Hi,

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

Cheers, Sérgio Peixoto

Next: Jeff King
Message 1 of 15 in “Change on check-attr behavior”
  1. Sérgio PeixotoJan 17, 2019
  2. Jeff KingJan 17, 2019
  3. Sérgio PeixotoJan 18, 2019
  4. Jeff KingJan 18, 2019
  5. attr: do not mark queried macros as unsetJeff King, Jan 18, 2019
  6. Jeff KingJan 18, 2019
  7. Stefan BellerJan 18, 2019
  8. Jeff KingJan 22, 2019
  9. Duy NguyenJan 22, 2019
  10. Junio C HamanoJan 22, 2019
  11. Duy NguyenJan 21, 2019
  12. Jeff KingJan 22, 2019
  13. Duy NguyenJan 22, 2019
  14. Junio C HamanoJan 22, 2019
  15. Jeff KingJan 23, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.