Replies: 3 comments 9 replies
The goal articulated here comes from the observation that you can run any command on any mutable revision in a repo since for example |
|
Sorry for opening as an issue, I didn't realise it should have been a discussion. |
|
Hey, I opened a PR around this here but really not interested in a google account. I thought the winning wording might be, "Strive to be modeless: If at all possible commands should work consistently and as the user expects in every situation." Use under whatever license the the docs are under at time of writing. Looks like apache. |
Uh oh!
There was an error while loading. Please reload this page.
In the docs there's a page about the core tenets of the project. One of those is "Having as few states as possible." I was wondering exactly what this meant. Is it about states of changes, the whole repo, interface modes?
It really isn't clear to me and I figure core tenets should be kept as clear as possible.
All reactions