From: Phillip Wood <phillip.wood123@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, Alejandro Colomar <alx@kernel.org>
Cc: git@vger.kernel.org, Nico Williams <nico@cryptonector.com>
Subject: Re: git-rebase-walk
Date: Sun, 4 Oct 2026 11:03:39 +0100 [thread overview]
Message-ID: <95796d0d-5928-4108-bc27-b7ace4459d2a@gmail.com> (raw)
In-Reply-To: <ar9TTB5nmPPAdABE@pks.im>
On 02/10/2026 07:46, Patrick Steinhardt wrote:
> On Thu, Oct 01, 2026 at 05:51:58PM +0200, Alejandro Colomar wrote:
>>
>> My script I use it in shadow-utils and in the Linux man-pages project,
>> and is in use today. I was wondering if there was interest in
>> integrating it to git(1).
>
> I guess the answer is "maybe". The fact that multiple folks have solved
> similar issues over the course of many years is an indicator that the
> funcitonality may be more generally useful. But it probably shouldn't be
> a separate script, so if we wanted to integrate it I'd think the best
> way forward would be to integrate it into git-rebase(1) directly.
I agree that would be the best way forward. Adding an "--incremental",
or "--progressive" option to rebase would be useful I think. For ease of
use, I have a strong preference for an implementation where "rebase
--continue" handles rebasing onto progressively more recent bases,
rather than the multi shot approach where the user has to run "git
rebase --incremental" multiple times. Having a multi-shot approach makes
it much less clear when we've successfully rebased onto the desired base.
Thanks
Phillip
> That's of course more involved though, so I understand in case you're
> not interested in doing that.
>
>> If not, I will likely provide it in the man-pages repository as a help
>> tool (which might end up packed by distros as part of manpages-utils).
>> Is that okay to you? (I ask mainly because it's using the git-
>> namespace for commands, so you should at lease be aware of it.)
>
> I mean overall this is our primary way of extension, by picking up
> utilities that have the "git-" prefix. So arguably you don't have to ask
> us for permission to do that.
>
> Whether it makes sense to distribute such a tool as part of
> manpages-utils is a different question, and one where I myself am of a
> split mind. But that feels more like a question for distributors rather
> than for us in the Git project.
>
> Thanks!
>
> Patrick
next prev parent reply other threads:[~2026-10-04 10:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 11:58 git-rebase-walk Alejandro Colomar
2026-10-01 13:22 ` git-rebase-walk Patrick Steinhardt
2026-10-01 15:51 ` git-rebase-walk Alejandro Colomar
2026-10-02 6:46 ` git-rebase-walk Patrick Steinhardt
2026-10-02 7:19 ` git-rebase-walk Alejandro Colomar
2026-10-03 19:37 ` git-rebase-walk Nico Williams
2026-10-04 10:03 ` Phillip Wood [this message]
2026-10-05 13:28 ` git-rebase-walk Alejandro Colomar
2026-10-05 13:37 ` git-rebase-walk Alejandro Colomar
2026-10-06 14:01 ` git-rebase-walk Phillip Wood
2026-10-06 14:58 ` git-rebase-walk Nico Williams
2026-10-06 16:45 ` git-rebase-walk Alejandro Colomar
2026-10-08 22:05 ` git-rebase-walk Alejandro Colomar
2026-10-08 22:07 ` git-rebase-walk Alejandro Colomar
2026-10-01 17:31 ` git-rebase-walk Junio C Hamano
2026-10-01 16:10 ` git-rebase-walk Nico Williams
2026-10-01 16:50 ` git-rebase-walk Alejandro Colomar
2026-10-01 17:40 ` git-rebase-walk Nico Williams
2026-10-01 20:29 ` git-rebase-walk Alejandro Colomar
2026-10-01 21:01 ` git-rebase-walk Nico Williams
2026-10-01 21:35 ` git-rebase-walk Nico Williams
2026-10-02 2:49 ` git-rebase-walk Simon Richter
2026-10-02 3:19 ` git-rebase-walk Nico Williams
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=95796d0d-5928-4108-bc27-b7ace4459d2a@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=alx@kernel.org \
--cc=git@vger.kernel.org \
--cc=nico@cryptonector.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/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