From: Efraim Flashner <efraim@flashner.co.il>
To: Fries <fries1234@protonmail.com>
Cc: 64804@debbugs.gnu.org, Juliana Sims <juli@incana.org>
Subject: [bug#64804] [PATCH 5/5] gnu: rust: Update to 1.71.
Date: Sun, 1 Oct 2023 10:10:51 +0300 [thread overview]
Message-ID: <ZRkbe0WrWns6RIg5@3900XT> (raw)
In-Reply-To: <5954949.lOV4Wx5bFT@pc>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On Mon, Jul 24, 2023 at 05:51:24AM +0000, Fries wrote:
> git-send-email wouldn't let me make a cover letter as the teams script thought
> it was an invalid patch so i'm going to send this email here.
>
> this patch series updates the rust package to rust 1.71.0! this means programs
> that require newer std api's like the stablized OnceCell API that was added in
> rust 1.70 can be used! i submitted this patch before and i got some feedback
> from juliana so i split my patches into a patch series.
>
> i don't know what branch this should go in but i checked the submitting patch
> webpage and i think as a rust update would mean a lot of rebuilding, i think
> it should go into the core-updates branch but i see theres also a rust-team
> branch. i don't know which one would be optimal.
Thanks for the patches!
Sorry it took me a while to get back to you, I had some time off during
the summer and needed a bit of a break after the last rust team merge.
I've applied patches 1, 2 and 4. I wasn't able to get rust-1.71 to build
so in the mean time I've bumped rust to 1.70 on the rust-team branch.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-01 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 6:38 [bug#64804] [PATCH] gnu: rust: Update to Rust 1.71.0 Fries via Guix-patches via
2023-07-23 20:38 ` Juliana Sims
2023-07-24 5:36 ` [bug#64804] [PATCH 1/5] gnu: rust: Add rust-1.69 Fries via Guix-patches via
2023-07-24 5:36 ` [bug#64804] [PATCH 2/5] gnu: rust: Add rust-1.70 Fries via Guix-patches via
2023-07-24 5:36 ` [bug#64804] [PATCH 3/5] gnu: rust: Add rust-1.71 Fries via Guix-patches via
2023-07-24 5:36 ` [bug#64804] [PATCH 4/5] gnu: rust: Add make-ignore-test-list function Fries via Guix-patches via
2023-07-24 5:36 ` [bug#64804] [PATCH 5/5] gnu: rust: Update to 1.71 Fries via Guix-patches via
2023-07-24 5:51 ` Fries via Guix-patches via
2023-10-01 7:10 ` Efraim Flashner [this message]
2023-09-30 15:40 ` [bug#64804] Please merge it Milan Svoboda
2023-10-01 9:30 ` Malte Frank Gerdes
2023-10-01 3:47 ` [bug#64804] [PATCH] gnu: rust: Update to Rust 1.71.0 jaeme via Guix-patches via
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=ZRkbe0WrWns6RIg5@3900XT \
--to=efraim@flashner.co.il \
--cc=64804@debbugs.gnu.org \
--cc=fries1234@protonmail.com \
--cc=juli@incana.org \
/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).