From: Collin Funk <collin.funk1@gmail.com>
To: Ezekiel Newren <ezekielnewren@gmail.com>
Cc: 20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks.im,
ps@pks.im, Johannes.Schindelin@gmx.de, ben.knoble@gmail.com,
cb@256bit.org, contact@hacktivis.me, eschwartz@gentoo.org,
git@vger.kernel.org, gitster@pobox.com, me@ttaylorr.com,
newren@gmail.com, phillip.wood123@gmail.com,
pierre-emmanuel.patry@embecosm.com, sam@gentoo.org,
sandals@crustytoothpaste.net
Subject: Re: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty
Date: Fri, 19 Sep 2025 11:14:54 -0700 [thread overview]
Message-ID: <87segiqpgh.fsf@gmail.com> (raw)
In-Reply-To: <CAH=ZcbCUL-rWw5E6p26T0039gs9q-P8iK5fp73-RzTzKiZ0zMQ@mail.gmail.com>
Ezekiel Newren <ezekielnewren@gmail.com> writes:
> On Fri, Sep 19, 2025 at 11:36 AM Sergey Fedorov
> <barracuda@macos-powerpc.org> wrote:
>> This will be a disaster, please consider not making rust mandatory.
>> It will break git for all systems without rust, in effect killing not only possibility to use GitHub and other git-based services, but also breaking build systems, since many ports – and package managers – rely on git to fetch sources.
>> As for local version control, git could be replaced with some alternative (likely inferior, but at least that is not the end).
>> There is no replacement, AFAIK, for build systems and for git-based online services.
>>
>> P. S. In case anyone wonders, this is personally relevant for me: I won’t be able to continue contributing to open-source anymore (at least certainly not like in past years) with git being unusable due to broken rust.
>
> The mailing list has had extremely heated debates about this, and
> there are many who would agree and disagree with you. So please try to
> read my comment as a genuine interest in trying to understand your
> situation. I would like to hear why making Rust mandatory would make
> using and contributing to Git insurmountable. We know for sure that
> NonStop currently does not support Rust at all, and that there are
> problems with porting Rust to Gentoo, but I'd like to hear what OSes
> and Architectures you use personally and professionally and why adding
> Rust would be a bad idea. Is it corporate policy? Is it that the Rust
> toolchain doesn't exist for your os/arch? Is it that Rust is a new
> language and isn't as battle tested as C? Something else?
>
> I believe that even "I don't know Rust and don't want to learn it."
> would be a valid comment to add as well. I think the discussion of
> Rust has been so hot because we (the Git community) don't understand
> everyone's situations and how they'll be affected, and what could
> possibly be done to address concerns.
Based on the domain of their email they use MacOS PowerPC. AFAIK LLVM
has not supported it for a long time.
Collin
next prev parent reply other threads:[~2025-09-19 18:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 17:36 [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty Sergey Fedorov
2025-09-19 17:56 ` Ezekiel Newren
2025-09-19 18:14 ` Collin Funk [this message]
2025-09-20 8:24 ` Florian Märkl
2025-09-22 15:59 ` Michael Orlitzky
2025-09-22 16:17 ` Sam James
2025-09-22 21:35 ` brian m. carlson
2025-09-22 21:47 ` Sam James
2025-09-23 5:05 ` Patrick Steinhardt
2025-09-22 23:23 ` Michael Orlitzky
-- strict thread matches above, loose matches on Subject: below --
2025-09-20 8:29 Sergey Fedorov
2025-09-20 18:39 ` rsbecker
2025-09-20 19:00 ` Ezekiel Newren
2025-09-20 19:25 ` Sam James
2025-09-20 23:17 ` rsbecker
2025-09-20 23:48 ` Ezekiel Newren
2025-09-21 1:15 ` rsbecker
2025-09-21 1:24 ` Ezekiel Newren
2025-09-21 3:18 ` rsbecker
2025-09-21 16:49 ` Ezekiel Newren
2025-09-21 23:07 ` rsbecker
2025-09-21 23:42 ` Ezekiel Newren
2025-09-22 16:21 ` rsbecker
2025-09-04 14:26 Patrick Steinhardt
2025-09-19 18:41 ` John Paul Adrian Glaubitz
2025-09-22 13:01 ` Patrick Steinhardt
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=87segiqpgh.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=ben.knoble@gmail.com \
--cc=cb@256bit.org \
--cc=contact@hacktivis.me \
--cc=eschwartz@gentoo.org \
--cc=ezekielnewren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=pierre-emmanuel.patry@embecosm.com \
--cc=ps@pks.im \
--cc=sam@gentoo.org \
--cc=sandals@crustytoothpaste.net \
/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;
as well as URLs for NNTP newsgroup(s).