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

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

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
Jan 3, 2009, 12:20 UTC
Message-ID
<20090103122001.GA20199@atjola.homenet>
In-Reply-To
<20090103011319.GA24149@seberino.org>
On 2009.01.02 17:13:19 -0800, chris@seberino.org wrote:
Show 11 quoted lines
> David
> 
> 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?

Deleting the branch also deletes the reflog, while using reset adds a new entry to the reflog. So returning the branch head to its previous state is pretty trivial if you used reset and might be pretty hard if you deleted the branch. HEAD's reflog should probably have the right entry as well, but chances are that it's hidden in a crapload of other entries, especially if you rebase often.

Björn
Previous: Sitaram Chamarty
Message 3 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.