From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: rust: Update to 1.67 - wanted - useful? ;-)
Date: Sat, 28 Jan 2023 14:37:45 +0100 [thread overview]
Message-ID: <ad360375-c70f-93a6-f2a0-177a55cd3129@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
Hi,
after the last drama I hardly dare to ask, but: are we interested in a
'rust 1.67' update, now that the update to 'rust 1.65' is in 'next'?
Changelog:
=>
https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1670-2023-01-26
First tests and build (I was curious): only lfs and rootfile updates are
needed.
*duckandcover*... ;-)
Best,
Matthias
next reply other threads:[~2023-01-28 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 13:37 Matthias Fischer [this message]
2023-01-29 14:27 ` Michael Tremer
2023-01-29 17:18 ` Matthias Fischer
2023-01-29 20:57 ` Michael Tremer
2023-01-30 17:48 ` Matthias Fischer
2023-01-30 18:34 ` Michael Tremer
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=ad360375-c70f-93a6-f2a0-177a55cd3129@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox