From: Thomas Guyot <tguyot@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Gerriko io <gerriko.iot@gmail.com>, git@vger.kernel.org
Subject: Re: Why is reflog so obscure?
Date: Tue, 12 Jul 2022 05:22:24 -0400 [thread overview]
Message-ID: <a8d2a61d-b86f-9b89-6391-36c58c390a12@gmail.com> (raw)
In-Reply-To: <Ys0e9MxIWQj/pVXx@coredump.intra.peff.net>
On 2022-07-12 03:12, Jeff King wrote:
> 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
next prev parent reply other threads:[~2022-07-12 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 21:02 Why is reflog so obscure? Gerriko io
2022-07-11 22:55 ` Thomas Guyot
2022-07-12 7:12 ` Jeff King
2022-07-12 9:22 ` Thomas Guyot [this message]
2022-07-12 14:23 ` Junio C Hamano
2022-07-12 15:18 ` Sergey Organov
2022-07-12 15:50 ` Junio C Hamano
2022-07-14 0:03 ` Thomas Guyot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8d2a61d-b86f-9b89-6391-36c58c390a12@gmail.com \
--to=tguyot@gmail.com \
--cc=gerriko.iot@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).