From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: "D. Ben Knoble" <ben.knoble+github@gmail.com>,
git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH 0/8] history: introduce "split" subcommand
Date: Mon, 16 Mar 2026 08:13:26 +0100 [thread overview]
Message-ID: <abetlsCTZaWPNK6U@pks.im> (raw)
In-Reply-To: <xmqqy0jv1hor.fsf@gitster.g>
On Fri, Mar 13, 2026 at 03:35:32PM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > this patch series introduces `git history split` as an easy way to split
> > up one commit into multiple commits. This subcommand has already been
> > introduced in earlier versions of my git-history(1) patch series, but I
> > eventually decided to evict them from this series so that we can rather
> > focus more on basic decisions.
>
> We saw a few exchanges and comments but didn't see an blocker.
> Everybody happy with the series?
There wasn't a ton of discussion on this series, but a lot of it already
happened back when it was still part of the initial git-history(1)
introduction. So it has already evolved significantly, even if that's
not quite visible here.
From my perspective this is ready to go.
Thanks!
Patrick
prev parent reply other threads:[~2026-03-16 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 12:13 [PATCH 0/8] history: introduce "split" subcommand Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 1/8] add-patch: split out header from "add-interactive.h" Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 2/8] add-patch: split out `struct interactive_options` Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 3/8] add-patch: remove dependency on "add-interactive" subsystem Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 4/8] add-patch: add support for in-memory index patching Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 5/8] add-patch: allow disabling editing of hunks Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 6/8] cache-tree: allow writing in-memory index as tree Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 7/8] builtin/history: split out extended function to create commits Patrick Steinhardt
2026-03-03 18:43 ` D. Ben Knoble
2026-03-11 9:26 ` Patrick Steinhardt
2026-03-02 12:13 ` [PATCH 8/8] builtin/history: implement "split" subcommand Patrick Steinhardt
2026-03-03 18:47 ` D. Ben Knoble
2026-03-11 9:26 ` Patrick Steinhardt
2026-03-03 18:41 ` [PATCH 0/8] history: introduce " D. Ben Knoble
2026-03-13 22:35 ` Junio C Hamano
2026-03-16 7:13 ` Patrick Steinhardt [this message]
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=abetlsCTZaWPNK6U@pks.im \
--to=ps@pks.im \
--cc=ben.knoble+github@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.