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

Re: Why is reflog so obscure?

From
Jeff King <peff@peff.net>
Date
Jul 12, 2022, 07:12 UTC
Message-ID
<Ys0e9MxIWQj/pVXx@coredump.intra.peff.net>
In-Reply-To
<f0bb8ee8-9b38-45a7-a54b-24cf245bb3c8@gmail.com>
On Mon, Jul 11, 2022 at 06:55:09PM -0400, Thomas Guyot wrote:
Show 5 quoted lines
> The reflog is simply a log of where you've been, in descending order (latest
> entry first), and is branch agnostic. It show every commit you've been on
> from latest to oldest, and each entry can be heads, tags, or detached
> commits. Some operations like rebase may even generate multiple entries if
> it's done in multiple steps (ex conflicts resolution).

This is right with one caveat: the HEAD reflog is branch agnostic. But there is a separate reflog for each individual branch, as well.

-Peff
Previous: Thomas GuyotNext: Thomas Guyot
Message 3 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.