From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: sundeep.kokkonda@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/9] rust: Upgrade 1.75.0->1.76.0
Date: Mon, 01 Jul 2024 12:36:15 +0100 [thread overview]
Message-ID: <acda968a19cc0e753ab7204ef6abe69bcf67f985.camel@linuxfoundation.org> (raw)
In-Reply-To: <25279.1719827797295861988@lists.openembedded.org>
On Mon, 2024-07-01 at 02:56 -0700, Sundeep KOKKONDA via
lists.openembedded.org wrote:
> We intentionally dropped these packages from exclude list (informed
> to Richard earlier) to see the issue fixes with latest releases.
This kind of patch series should really have a cover letter explaining
that since most people were not part of that conversation we had.
To be clear, I said it was ok to send these patches for testing so we
could understand where we stood with newer versions of rust.
I did make it clear we do need to resolve the reproducibility issue
with 1.75 for scarthgap before we can merge things though.
Cheers,
Richard
next prev parent reply other threads:[~2024-07-01 11:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 9:26 [PATCH 1/9] rust: Oe-selftest fixes for rust v1.76 Yash.Shinde
2024-07-01 9:26 ` [PATCH 2/9] rust: Upgrade 1.75.0->1.76.0 Yash.Shinde
2024-07-01 9:50 ` Alexander Kanavin
2024-07-01 9:56 ` Sundeep KOKKONDA
2024-07-01 11:36 ` Richard Purdie [this message]
2024-07-01 9:26 ` [PATCH 3/9] rust: reproducibility issue fix with v1.76 Yash.Shinde
2024-07-01 9:26 ` [PATCH 4/9] rust: Oe-selftest changes for rust v1.77 Yash.Shinde
2024-07-01 9:26 ` [PATCH 5/9] rust: Upgrade 1.76.0->1.77.0 Yash.Shinde
2024-07-01 9:26 ` [PATCH 6/9] rust: Upgrade 1.77.0->1.77.1 Yash.Shinde
2024-07-01 9:26 ` [PATCH 7/9] rust: Upgrade 1.77.1->1.77.2 Yash.Shinde
2024-07-01 9:26 ` [PATCH 8/9] rust: Oe-selftest changes for rust v1.78 Yash.Shinde
2024-07-01 9:26 ` [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0 Yash.Shinde
2024-07-01 9:30 ` Yash Shinde
2024-07-01 16:47 ` [OE-core] " Richard Purdie
2024-07-02 12:36 ` Sundeep KOKKONDA
[not found] ` <17DE24B76261B84E.14163@lists.openembedded.org>
2024-07-02 8:59 ` [OE-core] " Richard Purdie
2024-07-02 12:37 ` Sundeep KOKKONDA
2024-07-02 14:12 ` [OE-core] " Richard Purdie
2024-07-02 15:08 ` Ross Burton
2024-07-02 17:37 ` Sundeep KOKKONDA
2024-07-03 8:14 ` [OE-core] " Richard Purdie
2024-07-03 8:19 ` Sundeep KOKKONDA
2024-07-04 5:49 ` Yash Shinde
2024-07-04 5:58 ` Yash Shinde
2024-07-04 5:58 ` Yash Shinde
[not found] ` <Groupsio.2.31491.1720072149300569224@lists.openembedded.org>
2024-07-04 10:36 ` [OE-core] " Alexander Kanavin
[not found] ` <17DEFC31DA378080.5810@lists.openembedded.org>
2024-07-04 11:22 ` Alexander Kanavin
2024-07-04 11:44 ` Yash Shinde
2024-07-04 11:53 ` Ross Burton
2024-07-01 9:48 ` [OE-core] [PATCH 1/9] rust: Oe-selftest fixes for rust v1.76 Alex Kiernan
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=acda968a19cc0e753ab7204ef6abe69bcf67f985.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sundeep.kokkonda@windriver.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