Ramkumar Ramachandra <artag...@gmail.com> writes:
> Matthieu Moy wrote:
>> I disagree. A configuration option is something you set once, and then
>> forget about. A command, or a command-line option, is something you
>> explicitely add when you need it.
> You're making it out to be a much bigger difference than it actually
> is. Users will simply alias pull to 'pull --autostash' (a lot of them
> already alias it to pull --ff-only, and I'm going to fix this soon).
No, they don't. Git forbids redefining commands with aliases. They may
have an alias like "git pullauto" or so, but not "git pull".
> If your criticism were that git status doesn't show stash state, I
> agree with you.
There's not much we can do about it now, as Git cannot guess whether a
stash is to be re-applied later or just kept "in case". My main use of
"git stash" is "I want a reset --hard, but stash is safer", I wouldn't
want "status" to remind me when I have a stash because it is almost
always the case.
Showing the "autostash" status in "git status" would make sense OTOH,
but I agree that it's another topic.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html