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

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

From
Junio C Hamano <junkio@cox.net>
Date
Aug 24, 2005, 18:35 UTC
Message-ID
<7vk6ibdvy1.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vacj8nw5v.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 12 quoted lines
> Sam Ravnborg <sam@ravnborg.org> writes:
>
>> 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 do not have objections to removing --mixed, but I do not find
> --force/--prune any less confusing than --soft/--hard.  Its just
> a terminology so once people get used to it anything would do.
> But I agree that we need to come up with a good name for them.
> I do not think --force/--prune is it, though.

Names aside, I have a feeling that "git reset --hard HEAD" is what "git checkout -f HEAD" should have done. As it stands, the latter leaves files not in HEAD but in the previous tree behind.

Comments?
Previous: Yasushi SHOJI
Message 7 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.