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

Re: git reset --hard <commit> superfluous?

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Jan 3, 2009, 06:34 UTC
Message-ID
<slrnglu1ms.63u.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<20090103011319.GA24149@seberino.org>
On 2009-01-03, chris@seberino.org <chris@seberino.org> wrote:
Show 9 quoted lines
> git reset --hard <commit>
> "resets" the current branch head.
>
> Is this equivalent to deleting the branch
> and doing
>
> git branch <branch> <commit> ??
>
> So "git reset --hard" is syntactic sugar and 'unnecessary' right?

only if you don't have any local changes to the work tree or the index :-)

If you do, however, the reset throws them away, while the longer method tries to preserves them, to the point of not letting you switch if there are too many changes.

Previous: chris@seberino.orgNext: Björn Steinbrink
Message 2 of 3 in “git reset --hard <commit> superfluous?”
  1. chris@seberino.orgJan 3, 2009
  2. Sitaram ChamartyJan 3, 2009
  3. Björn SteinbrinkJan 3, 2009

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.