From: Patrick Steinhardt <ps@pks.im>
To: Alejandro Colomar <alx@kernel.org>
Cc: git@vger.kernel.org
Subject: Re: git-rebase-walk
Date: Thu, 1 Oct 2026 15:22:02 +0200 [thread overview]
Message-ID: <ar5eereSq91xldo-@pks.im> (raw)
In-Reply-To: <ar5KL4_IKXYbx3Sb@debian>
Hi,
On Thu, Oct 01, 2026 at 01:58:42PM +0200, Alejandro Colomar wrote:
> Hi!
>
> I use this little command to apply iterative rebases, which are easier
> to handle when there are large conflicts. Are you interested in it?
>
> $ cat $(which git-rebase-walk)
> #!/bin/bash
>
> set -Eeufo pipefail;
>
> git merge-base HEAD "$1" \
> | xargs -I{} git log --oneline {}.."$1" \
> | cut -f1 -d' ' \
> | tac \
> | while read -r c; do
> git rebase "$c";
> done;
>
> The source code is trivial, so I guess I don't need to explain much.
> It behaves quite nicely, IME.
>
> You may of course want to adapt it a little bit for merging in git(1).
> I could help improve it a little bit.
this reminds me a bit of git-imerge [1]. What this tool does is to
basically perform a merge between two branches incrementally using a
matrix. The tool tries to address exactly your use case, which is to
"present the user with one pairwise conflict at a time for resolution".
Maybe that tool is interesting to you. But it's certainly fallen a bit
out of date, as it hasn't received any updates for more than 6 years by
now. Chances are it stll works alright though.
Thanks!
Patrick
[1]: https://github.com/mhagger/git-imerge
next prev parent reply other threads:[~2026-10-01 13:22 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 ` Patrick Steinhardt [this message]
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 ` git-rebase-walk Phillip Wood
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=ar5eereSq91xldo-@pks.im \
--to=ps@pks.im \
--cc=alx@kernel.org \
--cc=git@vger.kernel.org \
/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