top | item 42147388 (no title) NautilusWave | 1 year ago So like ~/.ssh/ is bad? Or does it get grandfathered? discuss order hn newest Vilian|1 year ago SSH has the argument that they are older than the specification, now cargo, nah, a lot of application that use ssh hardcoded .ssh, cargo don't have that excuse Arch-TK|1 year ago I thought my comment addresses this specifically.Yes, it's bad. If you predate the specification then see options 2 (check), 3 (document) or 4 (come up with a new spec for opting in). ramon156|1 year ago I feel like a healthy mix is fine. Just like I wouldn't want my repo to be 90% cache, having 1-2 folders is fine.
Vilian|1 year ago SSH has the argument that they are older than the specification, now cargo, nah, a lot of application that use ssh hardcoded .ssh, cargo don't have that excuse
Arch-TK|1 year ago I thought my comment addresses this specifically.Yes, it's bad. If you predate the specification then see options 2 (check), 3 (document) or 4 (come up with a new spec for opting in).
ramon156|1 year ago I feel like a healthy mix is fine. Just like I wouldn't want my repo to be 90% cache, having 1-2 folders is fine.
Vilian|1 year ago
Arch-TK|1 year ago
Yes, it's bad. If you predate the specification then see options 2 (check), 3 (document) or 4 (come up with a new spec for opting in).
ramon156|1 year ago