Git development
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: rsbecker@nexbridge.com
Cc: 'Junio C Hamano' <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What will come after Git 2.56?
Date: Tue, 8 Sep 2026 15:59:25 +0000	[thread overview]
Message-ID: <aqAw3a3Ek0EZg0CH@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <010801dd3fa9$3277ae30$97670a90$@nexbridge.com>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On 2026-09-08 at 15:46:16, rsbecker@nexbridge.com wrote:
> On September 6, 2026 2:15 PM, brian m. carlson wrote:
> >Similarly, I am not aware of anyone who is seriously undertaking Rust support for
> >platforms that do not already support it, so I don't think that should be a blocker,
> >either.
> 
> Actually, I may have some news on that score. While it is unlikely to make 3.0, it
> could be soon after. Unfortunately, all info is NDA, so I cannot really publicise it
> at this point. I remain very hopeful.

I'm very pleased to hear that some progress might be being made.  I,
too, am hopeful that NonStop or other platforms might provide a suitable
Rust port that would work with Git.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]

      reply	other threads:[~2026-09-08 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06  7:03 What will come after Git 2.56? Junio C Hamano
2026-09-06 18:14 ` brian m. carlson
2026-09-07  8:23   ` Patrick Steinhardt
2026-09-07  9:30   ` Emily Shaffer
2026-09-08 15:46   ` rsbecker
2026-09-08 15:59     ` brian m. carlson [this message]

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=aqAw3a3Ek0EZg0CH@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rsbecker@nexbridge.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