git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 18:13 UTC

Re: [PATCH v2 0/3] contrib/subtree: reduce recursion during split

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 22, 2026, 09:43 UTC
Message-ID
<02c82c5c-6bc6-e298-3002-e6d322bdb957@gmx.de>
In-Reply-To
<cca575ae-e5dd-4a5d-bde2-f493a3e62a87@howdoi.land>
Hi Colin & Ian,
On Wed, 22 Apr 2026, Colin Stagner wrote:
Show 29 quoted lines
> 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

Previous: Colin StagnerNext: Ian Jackson
Message 17 of 22 in “contrib/subtree: reduce function side-effects”
  1. 1/3 contrib/subtree: reduce function side-effectsColin Stagner, Mar 5, 2026
  2. 2/3 contrib/subtree: functionalize split traversalColin Stagner, Mar 5, 2026
  3. 3/3 contrib/subtree: reduce recursion during splitColin Stagner, Mar 5, 2026
  4. 0/3 contrib/subtree: reduce recursion during splitColin Stagner, Mar 5, 2026
  5. Junio C HamanoMar 13, 2026
  6. Junio C HamanoMar 13, 2026
  7. Junio C HamanoApr 15, 2026
  8. Ben KnobleApr 15, 2026
  9. Ian JacksonApr 16, 2026
  10. Junio C HamanoApr 16, 2026
  11. Colin StagnerApr 17, 2026
  12. Ian JacksonApr 19, 2026
  13. Ben KnobleApr 20, 2026
  14. Junio C HamanoApr 20, 2026
  15. Ian JacksonApr 20, 2026
  16. Colin StagnerApr 21, 2026
  17. Johannes SchindelinApr 22, 2026
  18. git-subtree rewriteIan Jackson, Apr 22, 2026
  19. Junio C HamanoJun 1, 2026
  20. Ian JacksonJun 2, 2026
  21. Colin StagnerJun 3, 2026
  22. Ian JacksonJun 3, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.