git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 22, 2011, 17:43 UTC
Message-ID
<7vei1iyzw7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4E29A792.9020805@avtalion.name>
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.

Previous: Ori Avtalion
Message 2 of 2 in “reset: silent for some commands, verbose for others?”
  1. Ori AvtalionJul 22, 2011
  2. Junio C HamanoJul 22, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.