From: Sam James <sam@gentoo•org>
To: me@ttaylorr•com
Cc: git@vger•kernel.org
Subject: Re: [DISCUSS] Introducing Rust into the Git project
Date: Thu, 11 Jan 2024 11:45:07 +0000 [thread overview]
Message-ID: <87v880m6r3.fsf@gentoo.org> (raw)
In-Reply-To: <ZZ77NQkSuiRxRDwt@nand.local>
Something I'm a bit concerned about is that right now, neither
rustc_codegen_gcc nor gccrs are ready for use here.
We've had trouble getting things wired up for rustc_codegen_gcc
- which is not to speak against their wonderful efforts - because
the Rust community hasn't yet figured out how to handle things which
pure rustc supports yet. See
e.g. https://github.com/rust-lang/libc/pull/3032.
I think care should be taken in citing rustc_codegen_gcc and gccrs
as options for alternative platforms for now. They will hopefully
be great options in the future, but they aren't today, and they probably
won't be in the next 6 months at the least.
We also do use git heavily on platforms which rustc isn't supported
yet.
thanks,
sam
next prev parent reply other threads:[~2024-01-11 11:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 20:16 [DISCUSS] Introducing Rust into the Git project Taylor Blau
2024-01-10 21:57 ` Dragan Simic
2024-01-10 22:11 ` Junio C Hamano
2024-01-10 22:15 ` rsbecker
2024-01-10 22:26 ` Taylor Blau
2024-01-10 23:52 ` rsbecker
2024-01-11 0:59 ` Elijah Newren
2024-01-11 1:44 ` rsbecker
2024-01-11 2:21 ` Elijah Newren
2024-01-11 2:57 ` rsbecker
2024-01-11 5:06 ` Elijah Newren
2024-01-11 6:56 ` Patrick Steinhardt
2024-01-11 13:07 ` rsbecker
2024-01-11 2:55 ` brian m. carlson
2024-01-11 3:24 ` rsbecker
2024-01-11 20:07 ` Trevor Gross
2024-01-11 21:28 ` rsbecker
2024-01-11 23:23 ` Trevor Gross
2024-01-22 23:17 ` Defining a platform support policy (Was: [DISCUSS] Introducing Rust into the Git project) Emily Shaffer
2024-01-23 0:11 ` rsbecker
2024-01-23 0:57 ` Defining a platform support policy Junio C Hamano
2024-01-23 0:31 ` Junio C Hamano
2024-01-24 7:54 ` Defining a platform support policy (Was: [DISCUSS] Introducing Rust into the Git project) Elijah Newren
2024-01-10 23:40 ` [DISCUSS] Introducing Rust into the Git project brian m. carlson
2024-01-11 0:33 ` Elijah Newren
2024-01-11 5:39 ` Dragan Simic
2024-01-11 16:57 ` Elijah Newren
2024-01-17 21:30 ` Dragan Simic
2024-01-24 4:15 ` Elijah Newren
2024-01-24 5:14 ` Dragan Simic
2024-01-11 0:12 ` Elijah Newren
2024-01-11 5:33 ` Dragan Simic
2024-01-11 1:56 ` brian m. carlson
2024-01-11 11:45 ` Sam James [this message]
2024-01-11 23:48 ` brian m. carlson
2024-01-12 8:24 ` Sam James
2024-01-12 14:46 ` Antoni Boucher
2024-01-11 23:53 ` Trevor Gross
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=87v880m6r3.fsf@gentoo.org \
--to=sam@gentoo$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ttaylorr$(echo .)com \
/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