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

Re: How to restore the original head after `git-reset --hard master^`

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Oct 11, 2005, 16:58 UTC
Message-ID
<Pine.LNX.4.63.0510111240410.23242@iabervon.org>
In-Reply-To
<Pine.LNX.4.64.0510110856520.14597@g5.osdl.org>
On Tue, 11 Oct 2005, Linus Torvalds wrote:
Show 12 quoted lines
> On Tue, 11 Oct 2005, Ben Lau wrote:
> > 
> >   After involves the command `git-reset --hard master^` in a repository, 
> > the working tree , current head and index are restored to the parent of 
> > master. That includes the content of '.git/refs/head/master'. Although 
> > the original commit object is still existed , I couldn't find it back.
> > 
> >  Is there anyway to recover the original master branch ?
> 
> Just run "git-fsck-objects" and look at any dangling commits. The commit 
> and related objects are still there (unless you've run "git prune"), so 
> once you find the name of it, you're all done.

That reminds me: if you lose all of your refs, it's hard to get them back, because git-fsck-objects aborts if you don't specify any heads or have any refs. Is there some reason for this check?

	-Daniel
*This .sig left intentionally blank*
Previous: Linus TorvaldsNext: Linus Torvalds
Message 3 of 5 in “How to restore the original head after `git-reset --hard master^`”
  1. Ben LauOct 11, 2005
  2. Linus TorvaldsOct 11, 2005
  3. Daniel BarkalowOct 11, 2005
  4. Linus TorvaldsOct 11, 2005
  5. Junio C HamanoOct 11, 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.