Re: Command-line interface thoughts (ad-hominem attacks)
- From
- Michael Nahas <mike.nahas@gmail.com>
- Date
- Jun 8, 2011, 11:39 UTC
- Message-ID
- <BANLkTinoQCZhyhgw61u7c3eF4e5MEf+eFA@mail.gmail.com>
- In-Reply-To
- <201106081312.46377.jnareb@gmail.com>
On Wed, Jun 8, 2011 at 7:12 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> I don't quite think that we need "git diff NEXT WTREE"; the short > and sweet "git diff" is short for a reason,
To be clear, I'm not advocating and have never advocated getting rid of zero-argument "git diff". I've advocated that every (whole project) diff command should be expressible by a "git diff TREE1 TREE2". I'm fine with defaults if one or zero trees are specified. So "git diff" would default to "git diff NEXT WTREE".
> It is not obvious that "git reset" can be used for files, and it requires > bit of analysis that it resets index from HEAD:
...
> 4. "git reset -- <file>" must set index version of file from HEAD. > > Truth to be told I really just follow what "git status" tells me ;-)
I love those messages but if a user is relying on just copying a warning message, then they are learning anything. They're parroting. I believe a user interface should have concepts and commands that make sense, so that user will learn them and be able to apply them in other areas.
> -- > Jakub Narebski > Poland >