All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yash.Shinde@windriver.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0
Date: Fri, 28 Mar 2025 14:40:01 +0000	[thread overview]
Message-ID: <fc9c93b1523399820a1a3b72f2da021c2780c179.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250328143005.880998-2-Yash.Shinde@windriver.com>

On Fri, 2025-03-28 at 07:30 -0700, Yash Shinde via
lists.openembedded.org wrote:
> From: Yash Shinde <Yash.Shinde@windriver.com>
> 
> Rust stable version updated to 1.85.0
> https://blog.rust-lang.org/2025/02/20/Rust-1.85.0.html
> 
> Some of the major updates:
> 
> - Update LIC_FILES_CHKSUM in libstd-rs and rust recipes.

How did the license file change? Was the overall recipe LICENSE
affected?

You need to be clear about what changed and if LICENSE is impacted.

Cheers,

Richard


  reply	other threads:[~2025-03-28 14:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 14:30 [PATCH 1/3] rust: Update "do_update_snapshot" task for rust-snapshot.inc Yash.Shinde
2025-03-28 14:30 ` [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0 Yash.Shinde
2025-03-28 14:40   ` Richard Purdie [this message]
2025-03-28 18:39     ` [OE-core] " Alexander Kanavin
2025-03-31  5:51       ` Yash Shinde
2025-03-28 14:50   ` Patchtest results for " patchtest
2025-03-28 15:17   ` [OE-core] " Koen Kooi
2025-03-28 17:51     ` Richard Purdie
2025-03-31  5:52       ` Yash Shinde
2025-03-28 18:02     ` Khem Raj
2025-03-31  5:52       ` Yash Shinde
2025-03-28 20:56   ` Randy MacLeod
2025-03-29 15:26     ` Richard Purdie
2025-03-31  5:53       ` Yash Shinde
2025-03-28 14:30 ` [PATCH 3/3] rust: Upgrade 1.85.0->1.85.1 Yash.Shinde
2025-03-28 14:50   ` Patchtest results for " patchtest

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=fc9c93b1523399820a1a3b72f2da021c2780c179.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=Yash.Shinde@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 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.