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

Re: Supporting `git add -a <exclude submodules>`

From
Joanna Wang <jojwang@google.com>
Date
Oct 17, 2023, 20:59 UTC
Message-ID
<CAMmZTi-xOWxpzL1SvErgri0_gwvED5Vu2NfeGVcW7jCN8gyEDQ@mail.gmail.com>
> choose among attr:submodule, attr:type=<what>, attr:bits=<permbits>, decide what keyword to use

Whatever we choose, do we want to block these keywords from being used by folks in their .gitattributes files? That would break any existing usage of the keywords. Is this a concern?

Option A: To keep things working, we could add this support for attr, but then always prioritize whatever is set in .gitattributes. So this new behavior would only be triggered if the keywords (e.g. "submodule", "type", "bits") aren't set in .gitattributes (or w/e list of attributes are being read).

Option B: Or we could add this new behavior for `attr-bits:<permbits>` or just `bits:<permbits>`.

I personally don't see big UX differences between A and B. Any opinions on this?
Next: Junio C Hamano
Message 1 of 2 in “Re: Supporting `git add -a <exclude submodules>`”
  1. Joanna WangOct 17, 2023
  2. Junio C HamanoOct 17, 2023

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.