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

Re: OK, how should I have done this...

From
Tay Ray Chuan <rctay89@gmail.com>
Date
Nov 22, 2010, 14:29 UTC
Message-ID
<AANLkTim19WCCz6_iMrRj9cLU1-Q=MGAWnvYOc8=NBC_F@mail.gmail.com>
In-Reply-To
<AANLkTi=uxRfsy2vG+4CBJv8Vhjrr2roVOXeNLvPA+6U+@mail.gmail.com>
Hi,
On Mon, Nov 22, 2010 at 10:22 PM, Patrick Doyle <wpdster@gmail.com> wrote:
> That looks kinda scary to me.  The last time I played with git-reset,
> I ended up losing(*) the commit at the head of my branch.  ((*) Well,
> I didn't "lose" it in the sense of "it's gone forever", but I lost it
> in the sense of "it doesn't show up in git log anymore".)

That's the whole idea of git reset. If you want to see what the "lost" commit was, try git reflog; it's very likely at HEAD@{1}.

-- 
Cheers,
Ray Chuan
Previous: Patrick DoyleNext: Matthieu Moy
Message 4 of 7 in “OK, how should I have done this...”
  1. Patrick DoyleNov 22, 2010
  2. Matthieu MoyNov 22, 2010
  3. Patrick DoyleNov 22, 2010
  4. Tay Ray ChuanNov 22, 2010
  5. Matthieu MoyNov 22, 2010
  6. Junio C HamanoNov 23, 2010
  7. Patrick DoyleNov 23, 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.