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

Re: recovering orphaned commit

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jun 29, 2010, 15:24 UTC
Message-ID
<20100629152424.GE4724@debian>
In-Reply-To
<AANLkTiks6yPfdTACQwZlqv8PPPEg3RYGMx1Q1PjT0nRu@mail.gmail.com>
Hi Mahesh,
Mahesh Vaidya writes:
Show 9 quoted lines
>  I have a situation like this; 2 commits.
> 
> Example -
> 
>  2899684ed173063354b7fe4f5ec7216e7d953e2c	 <-- HEAD  ( say C1)
>  1ef67de1a0d6e97470a8c827d2989317600532ff                    ( say C2)
> 
> To see file at C2 ; I have done git reset --hard C2; I could see the file.
> Now want go to C1 ; Ho do I Determine C1  using git command ?
Use git-reflog (1) perhaps?
-- Ram
Previous: Shawn O. PearceNext: Jonathan Nieder
Message 3 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.