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

2 messages from 2011-07-22 to 2011-07-22. Participants: Ori Avtalion, Junio C Hamano.
Thread: https://gitlist.dev/t/27888

## Ori Avtalion, 2011-07-22 16:38

Subject: reset: silent for some commands, verbose for others?
Message-ID: <4E29A792.9020805@avtalion.name>
URL: https://gitlist.dev/e/4E29A792.9020805%40avtalion.name

```
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, 2011-07-22 17:43

Subject: Re: reset: silent for some commands, verbose for others?
Message-ID: <7vei1iyzw7.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vei1iyzw7.fsf%40alter.siamese.dyndns.org
In-Reply-To: <4E29A792.9020805@avtalion.name>

```
Ori Avtalion <ori@avtalion.name> writes:

> 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.

```