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

Re: [PATCH] Introduce "reset type" flag to "git reset"

From
Sam Ravnborg <sam@ravnborg.org>
Date
Aug 23, 2005, 20:26 UTC
Message-ID
<20050823202637.GA8061@mars.ravnborg.org>
In-Reply-To
<7vu0hhzcj1.fsf@assigned-by-dhcp.cox.net>
> I am not sure what mixed reset (the current behaviour) is good
> for.  If nobody comes up with a good use case it may not be a
> bad idea to remove it.

Using the principle of minimum suprise the --mixed should be removed. --soft - undo the commit leaving all changes. --hard - undo the commit and removing all changes

I'm a cogito user so not used to got options. But --soft, --hard looks rather confusing to me.

Something like --force or --prune may be a bit more intuitive, and let default behaviour be the one you name --soft for now.

I think it would make sense to be able to specify the topmost SHA1 (or HEAD:5 or HEAD^^^^^) from where the reset should start.

	Sam
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 7 in “Introduce "reset type" flag to "git reset"”
  1. Introduce "reset type" flag to "git reset"Junio C Hamano, Aug 23, 2005
  2. Sam RavnborgAug 23, 2005
  3. Junio C HamanoAug 23, 2005
  4. Yasushi SHOJIAug 24, 2005
  5. Junio C HamanoAug 24, 2005
  6. Yasushi SHOJIAug 24, 2005
  7. Junio C HamanoAug 24, 2005

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.