From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: El Mehdi YOUNES via buildroot <buildroot@buildroot.org>,
El Mehdi YOUNES <elmehdi.younes@smile.fr>,
Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Joseph Kogut <joseph.kogut@gmail.com>,
David Pierret <david.pierret@smile.fr>,
Danilo Bargen <mail@dbrgn.ch>,
Graeme Smecher <gsmecher@threespeedlogic.com>,
James Hilliard <james.hilliard1@gmail.com>,
Sam Voss <sam.voss@gmail.com>,
Torben Voltmer <mail@t-voltmer.net>,
Saeed Kazemi <kazemi.ms@gmail.com>,
Alex Michel <alex.michel@wiedemann-group.com>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [Buildroot] [PATCH 0/4] package/rust: rust upgrade to version 1.86.0
Date: Fri, 16 May 2025 16:50:51 +0200 [thread overview]
Message-ID: <20250516165051.3f20224d@windsurf> (raw)
In-Reply-To: <4f3b7a04-418b-4563-b556-60c5d6f2c34b@gmx.de>
On Fri, 16 May 2025 15:40:00 +0200
Fiona Klute <fiona.klute@gmx.de> wrote:
> it seems my patch to replace deprecated the .cargo/config [1] that was
> discussed in that thread [2] has been missed. Is there any chance to
> still squeeze it in? The problem is that if applied separately it'll
> need a separate version bump for the generated cargo archives, but I'm
> not sure if that's avoidable now (as the changes have been pushed
> already). :-(
Dang, I missed that! Let's see what we can do about this, I'll discuss
with the other maintainers.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-05-16 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:47 [Buildroot] [PATCH 0/4] package/rust: rust upgrade to version 1.86.0 El Mehdi YOUNES via buildroot
2025-04-22 7:47 ` [Buildroot] [PATCH 1/4] package/rust: fix bootstrap with Rust≥1.83 El Mehdi YOUNES via buildroot
2025-04-22 7:47 ` [Buildroot] [PATCH 2/4] package/rust: bump to version 1.86.0 El Mehdi YOUNES via buildroot
2025-04-22 7:47 ` [Buildroot] [PATCH 3/4] package/pkg-download: switch from cargo2 to cargo3 El Mehdi YOUNES via buildroot
2025-04-22 7:47 ` [Buildroot] [PATCH 4/4] package: update all hashes after cargo3 switch El Mehdi YOUNES via buildroot
2025-04-22 10:30 ` [Buildroot] [PATCH 0/4] package/rust: rust upgrade to version 1.86.0 Fiona Klute via buildroot
2025-04-22 11:40 ` El Mehdi YOUNES via buildroot
2025-05-16 11:32 ` Thomas Petazzoni via buildroot
2025-05-16 13:40 ` Fiona Klute via buildroot
2025-05-16 14:50 ` Thomas Petazzoni via buildroot [this message]
2025-05-16 14:57 ` El Mehdi YOUNES via buildroot
2025-05-19 12:23 ` Fiona Klute via buildroot
2025-05-19 13:28 ` Thomas Petazzoni via buildroot
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=20250516165051.3f20224d@windsurf \
--to=buildroot@buildroot.org \
--cc=alex.michel@wiedemann-group.com \
--cc=david.pierret@smile.fr \
--cc=elmehdi.younes@smile.fr \
--cc=eric.le.bihan.dev@free.fr \
--cc=fiona.klute@gmx.de \
--cc=gsmecher@threespeedlogic.com \
--cc=james.hilliard1@gmail.com \
--cc=joseph.kogut@gmail.com \
--cc=kazemi.ms@gmail.com \
--cc=mail@dbrgn.ch \
--cc=mail@t-voltmer.net \
--cc=mika.westerberg@linux.intel.com \
--cc=sam.voss@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ycliang@andestech.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox