From: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Harald Nordgren <haraldnordgren@gmail.com>
Subject: [PATCH 0/3] reflog: add --operations and --historical-branch
Date: Thu, 15 Oct 2026 13:13:55 +0000 [thread overview]
Message-ID: <pull.2448.git.git.1792070038.gitgitgadget@gmail.com> (raw)
Create a better reflog. Follows the discussion in
https://lore.kernel.org/git/akZfm-igZKeHaDST@pks.im/.
"git reflog" lists every step of a rebase and every branch switch, which
makes it hard to see what was done and on which branch. This adds two
options to "git reflog" and "git log -g":
* --operations shows one entry per command, folding a rebase into the entry
that finished or aborted it, and leaves out entries that change no
branch.
* --historical-branch decorates each entry with the branch HEAD was on when
it was recorded.
Harald Nordgren (3):
reflog: name the strings that mark switches, renames and rebase steps
reflog: add --operations to show one entry per command
reflog: add --historical-branch to name the branch of each entry
Documentation/git-reflog.adoc | 4 +
Documentation/rev-list-options.adoc | 19 +++
builtin/branch.c | 3 +-
builtin/checkout.c | 3 +-
builtin/rebase.c | 17 +--
log-tree.c | 21 +++
object-name.c | 3 +-
reflog-walk.c | 172 ++++++++++++++++++++++--
reflog-walk.h | 3 +
reflog.h | 6 +
revision.c | 14 ++
revision.h | 2 +
sequencer.c | 13 +-
t/t1414-reflog-walk.sh | 198 ++++++++++++++++++++++++++++
wt-status.c | 3 +-
15 files changed, 455 insertions(+), 26 deletions(-)
base-commit: 6de20f6092dcf9bdb1c8efe03db4b70c82b423dd
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2448%2FHaraldNordgren%2Freflog-operations-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2448/HaraldNordgren/reflog-operations-v1
Pull-Request: https://github.com/git/git/pull/2448
--
gitgitgadget
next reply other threads:[~2026-10-15 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 13:13 Harald Nordgren via GitGitGadget [this message]
2026-10-15 13:13 ` [PATCH 1/3] reflog: name the strings that mark switches, renames and rebase steps Harald Nordgren via GitGitGadget
2026-10-15 13:13 ` [PATCH 2/3] reflog: add --operations to show one entry per command Harald Nordgren via GitGitGadget
2026-10-15 13:13 ` [PATCH 3/3] reflog: add --historical-branch to name the branch of each entry Harald Nordgren via GitGitGadget
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=pull.2448.git.git.1792070038.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.com \
/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