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

Re: recovering orphaned commit

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jun 29, 2010, 15:26 UTC
Message-ID
<20100629152606.GA7202@burratino>
In-Reply-To
<AANLkTiks6yPfdTACQwZlqv8PPPEg3RYGMx1Q1PjT0nRu@mail.gmail.com>
Hi Mahesh,
Mahesh Vaidya wrote:
>  2899684ed173063354b7fe4f5ec7216e7d953e2c	 <-- HEAD  ( say C1)
>  1ef67de1a0d6e97470a8c827d2989317600532ff                    ( say C2)
> 
> To see file at C2 ; I have done git reset --hard C2

For the future, ‘git checkout C2’ might work better for this task. Unlike ‘git reset’, it does not change where the current branch head points, so when you’re done exploring you can get back to where you were with ‘git checkout topic’ (where topic is the name of the branch --- e.g., master).

> Now want go to C1 ; Ho do I Determine C1  using git command ?
git log -g HEAD

Hope that helps, Jonathan

Previous: Ramkumar RamachandraNext: Wincent Colaiuta
Message 4 of 5 in “recovering orphaned commit”
  1. Mahesh VaidyaJun 29, 2010
  2. Shawn O. PearceJun 29, 2010
  3. Ramkumar RamachandraJun 29, 2010
  4. Jonathan NiederJun 29, 2010
  5. Wincent ColaiutaJun 29, 2010

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.