From: Malte Frank Gerdes <malte.f.gerdes@gmail.com>
To: Milan Svoboda <milan.svoboda@centrum.cz>
Cc: 64804@debbugs.gnu.org
Subject: [bug#64804] Please merge it
Date: Sun, 01 Oct 2023 11:30:16 +0200 [thread overview]
Message-ID: <861qeebsby.fsf@gmail.com> (raw)
In-Reply-To: <a366f510-0f9e-c82f-ddc5-71034ba45668@centrum.cz>
Hi,
such rust related changes are targeted at the rust team branch. IIRC
the rust team is a one-man army, so it absolutely possible that things
take a while :/.
But reading #64804, Efraim already bumped rust to 1.70 on the rust-team
branch, so it will be available after the next rust-team merge. In the
meantime you'd have to use the rust-team branch if you really want to
use rust-1.70.
mfg²
Milan Svoboda <milan.svoboda@centrum.cz> writes:
> Hello,
>
> it would be wonderful if this could be merged. I am trying to package broot
> (command line file manager) and one of it's dependency requires rust 1.70.0.
>
> Pretty please.
next prev parent reply other threads:[~2023-10-01 9:34 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
2023-09-30 15:40 ` [bug#64804] Please merge it Milan Svoboda
2023-10-01 9:30 ` Malte Frank Gerdes [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861qeebsby.fsf@gmail.com \
--to=malte.f.gerdes@gmail.com \
--cc=64804@debbugs.gnu.org \
--cc=milan.svoboda@centrum.cz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.