From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Colin Stagner <ask+git@howdoi.land>
Cc: Ian Jackson <ijackson@chiark.greenend.org.uk>,
git@vger.kernel.org, Christian Heusel <christian@heusel.eu>,
george@mail.dietrich.pub, Christian Hesse <list@eworm.de>,
Phillip Wood <phillip.wood@dunelm.org.uk>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2 0/3] contrib/subtree: reduce recursion during split
Date: Wed, 22 Apr 2026 11:43:29 +0200 (CEST) [thread overview]
Message-ID: <02c82c5c-6bc6-e298-3002-e6d322bdb957@gmx.de> (raw)
In-Reply-To: <cca575ae-e5dd-4a5d-bde2-f493a3e62a87@howdoi.land>
Hi Colin & Ian,
On Wed, 22 Apr 2026, Colin Stagner wrote:
> On 4/20/26 04:57, Ian Jackson wrote:
>
> > I need to think about this some more but I doubt this can be made to
> > work well without more significant changes, including to the data
> > model. There would have to be some kind of compatibility arrangement
> > to handle existing histories.
>
> I would take a look at the test-cases for git-subtree.sh, which document
> some of the kinds of issues you will encounter. They may help you test
> compatibility.
>
> Anything you can do to limit breakage to "opt-in" points-in-time only
> would be greatly appreciated.
>
> > Colin, is that OK with you?
>
> You can name it and develop it however you like. No need to ask
> permission here.
>
> (For the record, I'm also not the maintainer of contrib/git-subtree.
> I've just been trying to fix a few issues with it.)
>
> > If you would prefer, I could choose a different name for the
> > resulting program.
>
> If I were writing it, I would give the new program a different name but
> perhaps provide a "compile-time" way to set it to "git-subtree" instead.
> My reason for this is that it may need to exist with the legacy script
> for awhile, and it's good to be able to tell them apart.
I just wanted to chime in to cheer you on, I've been following this
Rust-based `git-subtree` idea with interest. You may know it already, Git
for Windows is shipping `git subtree` with its installers for ages, and
given the abysmal performance characteristics of shell-based Git commands
on Windows, it would be really good to replace the shell-scripted version
with the Rust version (also to ensure proper error handling, which is
hard to make comprehensive in Unix shell scripts).
Thank you for pushing this forward!
Ciao,
Johannes
next prev parent reply other threads:[~2026-04-22 9:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 20:17 [PATCH 0/3] contrib/subtree: reduce recursion during split Colin Stagner
2026-02-15 20:17 ` [PATCH 1/3] contrib/subtree: reduce function side-effects Colin Stagner
2026-02-15 20:17 ` [PATCH 2/3] contrib/subtree: functionalize split traversal Colin Stagner
2026-02-15 20:17 ` [PATCH 3/3] contrib/subtree: reduce recursion during split Colin Stagner
2026-03-05 23:55 ` [PATCH v2 0/3] " Colin Stagner
2026-03-05 23:55 ` [PATCH v2 1/3] contrib/subtree: reduce function side-effects Colin Stagner
2026-03-05 23:55 ` [PATCH v2 2/3] contrib/subtree: functionalize split traversal Colin Stagner
2026-03-05 23:55 ` [PATCH v2 3/3] contrib/subtree: reduce recursion during split Colin Stagner
2026-03-13 22:51 ` [PATCH v2 0/3] " Junio C Hamano
2026-03-13 23:06 ` Junio C Hamano
2026-04-15 17:58 ` Junio C Hamano
2026-04-15 21:39 ` Ben Knoble
2026-04-16 13:25 ` Ian Jackson
2026-04-16 19:34 ` Junio C Hamano
2026-04-17 4:50 ` Colin Stagner
2026-04-19 19:55 ` Ian Jackson
2026-04-20 1:09 ` Ben Knoble
2026-04-20 1:50 ` Junio C Hamano
2026-04-20 9:57 ` Ian Jackson
2026-04-21 5:07 ` Colin Stagner
2026-04-22 9:43 ` Johannes Schindelin [this message]
2026-04-22 17:12 ` git-subtree rewrite Ian Jackson
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=02c82c5c-6bc6-e298-3002-e6d322bdb957@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=ask+git@howdoi.land \
--cc=christian@heusel.eu \
--cc=george@mail.dietrich.pub \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ijackson@chiark.greenend.org.uk \
--cc=list@eworm.de \
--cc=phillip.wood@dunelm.org.uk \
/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