reset: silent for some commands, verbose for others?

Ori Avtalion· Jul 22, 2011, 16:38 UTC · lore

Looking at the reset's command third form:

  reset [--soft | --mixed | --hard | --merge | --keep] [-q] [<commit>]

* --soft, --merge, --keep are silent.
* --mixed prints "Unstaged changes after reset: ..."
* --hard prints "HAED is now at..."

If all of those commands move HEAD, shouldn't all of them print "HEAD is now at..."?

Why should only --mixed print the list of unstaged files? e.g. Isn't it useful for --soft to give a list of "Staged changes"?

Junio C Hamano· Jul 22, 2011, 17:43 UTC · re: Ori Avtalion · lore

Re: reset: silent for some commands, verbose for others?

Ori Avtalion <ori@avtalion.name> writes:

Show 13 quoted lines

> Looking at the reset's command third form:
>
>   reset [--soft | --mixed | --hard | --merge | --keep] [-q] [<commit>]
>
> * --soft, --merge, --keep are silent.
> * --mixed prints "Unstaged changes after reset: ..."
> * --hard prints "HAED is now at..."
>
> If all of those commands move HEAD, shouldn't all of them print "HEAD is
> now at..."?
>
> Why should only --mixed print the list of unstaged files? e.g. Isn't it
> useful for --soft to give a list of "Staged changes"?

I would say not, as you would use "soft" only when you _know_ what you have in the index is what you want, and more importantly it does not change what is in the index, unlike "mixed" variant.