From: Maxime Devos <maximedevos@telenet.be>
To: Pierre Langlois <pierre.langlois@gmx.com>,
54580@debbugs.gnu.org, 54439@debbugs.gnu.org
Subject: [bug#54439] [bug#54580] [PATCH staging?] gnu: mrustc: Update to 0.10.
Date: Sat, 26 Mar 2022 16:09:28 +0100 [thread overview]
Message-ID: <730f00e80ab8469d6ce783ffff13cee76c533810.camel@telenet.be> (raw)
In-Reply-To: <87lewwbzwy.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Pierre Langlois schreef op za 26-03-2022 om 13:27 [+0000]:
> That being said, I wasn't entirely sure where this patch should go,
> ideally it would be good to have a staging branch rather than
> core-updates, WDYT? Maybe we can do this along with a rust version
> update?
While it would cause many rebuilds, it seems highly unlikely to
actually break anything, as it only changes some early parts of the
Rust bootstrapping process, so build farm capacity permitting, I would
go with a staging branch (not necessarily the "staging" branch, just
_a_ staging branch).
Doing it together with a rust version update seems reasonable to me
(see <https://issues.guix.gnu.org/54439#10>).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-03-26 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 13:27 [bug#54580] [PATCH staging?] gnu: mrustc: Update to 0.10 Pierre Langlois
2022-03-26 14:16 ` Pierre Langlois
2022-03-26 14:58 ` Maxime Devos
2022-03-26 15:05 ` Pierre Langlois
2022-05-09 14:22 ` Efraim Flashner
2022-05-09 22:12 ` bug#54580: " Pierre Langlois
2022-03-26 15:09 ` Maxime Devos [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=730f00e80ab8469d6ce783ffff13cee76c533810.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54439@debbugs.gnu.org \
--cc=54580@debbugs.gnu.org \
--cc=pierre.langlois@gmx.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).