Re: Why is reflog so obscure?

From: Thomas Guyot <tguyot@gmail.com>
Date: Jul 12, 2022, 09:22 UTC
Message-ID: <a8d2a61d-b86f-9b89-6391-36c58c390a12@gmail.com>
In-Reply-To: <Ys0e9MxIWQj/pVXx@coredump.intra.peff.net>

On 2022-07-12 03:12, Jeff King wrote:

Show 9 quoted lines

> On Mon, Jul 11, 2022 at 06:55:09PM -0400, Thomas Guyot wrote:
>
>> 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.

Hi Jeff,

Thanks for clarifying that - I suspected it since we can do <branch>@{<date>} although I didn't find any reference branch reflogs in the documentation. I could've missed it... Is there a way to read a branch reflog?

-- Thomas