> 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?
