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

Why is reflog so obscure?

From
GIGerriko io <gerriko.iot@gmail.com>
Date
Jul 11, 2022, 21:02 UTC
Message-ID
<CALF=2ANoq1eL-RqK_dLaVThoxbvfhzgPJXFHyD1kX8CFCPx3XA@mail.gmail.com>

I am trying to make sense of reflog as I need to know this to use revert and reset properly.

I cannot find the most basic information in the git documentation or online.

Surely the most basic question is whether the reflog is sequential or just random logs or whether it is in time ascending or descending order.

Without this information I am left baffled and have to guess what this line means out of the many:

a0bbd34 (HEAD -> master, origin/master, origin/main) refs/remotes/origin/main@{0}: update by push

Why does it have to be so obscure?
Next: Thomas Guyot
Message 1 of 8 in “Why is reflog so obscure?”
  1. Gerriko ioJul 11, 2022
  2. Thomas GuyotJul 11, 2022
  3. Jeff KingJul 12, 2022
  4. Thomas GuyotJul 12, 2022
  5. Junio C HamanoJul 12, 2022
  6. Sergey OrganovJul 12, 2022
  7. Junio C HamanoJul 12, 2022
  8. Thomas GuyotJul 14, 2022

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.