From: Ian Jackson <ijackson@chiark•greenend.org.uk>
To: Junio C Hamano <gitster@pobox•com>
Cc: Colin Stagner <ask+git@howdoi•land>,
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>
Subject: Re: [PATCH v2 0/3] contrib/subtree: reduce recursion during split
Date: Tue, 2 Jun 2026 10:06:15 +0100 [thread overview]
Message-ID: <27166.40199.68450.953526@chiark.greenend.org.uk> (raw)
In-Reply-To: <xmqqv7c13o5l.fsf@gitster.g>
Junio C Hamano writes ("Re: [PATCH v2 0/3] contrib/subtree: reduce recursion during split"):
> So after this message the thread went dark (except for a side
> discussion about rewriting subtree in Rust, which I do think it is a
> good direction to go in the longer term).
I'm indeed still working on this. Given other things on my plate it
will be months rather than weeks before I have anything anyone one
might want to use.
> While I do agree that avoiding bash-isms in the main part of Git and
> sticking to vanilla POSIX has merit, this particular one seems more
> like an artificial limit imposed by dash than sticking to the POSIX
> as the common denoninator, at least to me.
I would be in favour of switching to bash, making bash a dependency
for this script. We could use the env trick to support platforms that
don't have it in /bin.
Ian.
--
Ian Jackson <ijackson@chiark•greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
next prev parent reply other threads:[~2026-06-02 9:41 UTC|newest]
Thread overview: 26+ 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
2026-04-22 17:12 ` git-subtree rewrite Ian Jackson
2026-06-01 22:13 ` [PATCH v2 0/3] contrib/subtree: reduce recursion during split Junio C Hamano
2026-06-02 9:06 ` Ian Jackson [this message]
2026-06-03 1:37 ` Colin Stagner
2026-06-03 9:12 ` 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=27166.40199.68450.953526@chiark.greenend.org.uk \
--to=ijackson@chiark$(echo .)greenend.org.uk \
--cc=ask+git@howdoi$(echo .)land \
--cc=christian@heusel$(echo .)eu \
--cc=george@mail$(echo .)dietrich.pub \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=list@eworm$(echo .)de \
--cc=phillip.wood@dunelm$(echo .)org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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