From: Ian Jackson <ijackson@chiark.greenend.org.uk>
To: Colin Stagner <ask+git@howdoi.land>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/2] git-subtree: Bail out if we find output from Rust rewrite [and 1 more messages]
Date: Sun, 12 Jul 2026 09:22:20 +0100 [thread overview]
Message-ID: <27219.20156.438730.881821@chiark.greenend.org.uk> (raw)
In-Reply-To: <a8c72dcd-f8d7-47ce-a4b2-ebcd4188875e@howdoi.land>
Colin Stagner writes ("Re: [PATCH 1/2] git-subtree: Bail out if we find output from Rust rewrite [and 1 more messages]"):
> On 7/11/26 18:04, Junio C Hamano wrote:
> > So, is there a conclusion after reviewing this?
>
> I think we're expecting a reroll, but this looks like the way forward.
Yes. Please bear with me, I'm travelling for a few days.
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-07-12 8:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 11:58 [PATCH 0/2] git-subtree: Bail out if we find output from Rust rewrite Ian Jackson
2026-07-06 11:58 ` [PATCH 1/2] " Ian Jackson
2026-07-06 14:44 ` Junio C Hamano
2026-07-06 15:03 ` Ian Jackson
2026-07-06 20:16 ` Junio C Hamano
2026-07-09 1:49 ` Colin Stagner
2026-07-06 11:58 ` [PATCH 2/2] git-subtree: Bail out if we find output from Rust rewrite (test) Ian Jackson
2026-07-09 1:59 ` Colin Stagner
2026-07-09 9:36 ` [PATCH 1/2] git-subtree: Bail out if we find output from Rust rewrite [and 1 more messages] Ian Jackson
2026-07-09 13:19 ` Phillip Wood
2026-07-09 22:43 ` Colin Stagner
2026-07-10 12:20 ` Ian Jackson
2026-07-15 3:47 ` Colin Stagner
2026-07-11 13:41 ` D. Ben Knoble
2026-07-11 19:58 ` Ian Jackson
2026-07-11 23:04 ` Junio C Hamano
2026-07-11 23:37 ` Colin Stagner
2026-07-12 8:22 ` Ian Jackson [this message]
2026-07-12 13:42 ` Junio C Hamano
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=27219.20156.438730.881821@chiark.greenend.org.uk \
--to=ijackson@chiark.greenend.org.uk \
--cc=Johannes.Schindelin@gmx.de \
--cc=ask+git@howdoi.land \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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