Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] rust: Upgrade 1.74.1 -> 1.75.0
Date: Thu, 11 Jan 2024 06:54:34 -0800	[thread overview]
Message-ID: <26286.1704984874999023341@lists.openembedded.org> (raw)
In-Reply-To: <CAO5Uq5TfNcuKkYX2krym5uN5t+ThbQ29Y8gfhq9kmLwYyHXfjQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 290 bytes --]

On Tue, Jan 2, 2024 at 02:54 PM, Alex Kiernan wrote:

> 
> Closing this off - for whatever reason the buildpaths check wasn't
> getting run when I was testing stuff, so what I thought was a fix,
> wasn't.

Hello Alex,

Are you working on fixing this issue?

Thanks,
Sundeep K.

[-- Attachment #2: Type: text/html, Size: 341 bytes --]

  reply	other threads:[~2024-01-11 14:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 15:49 [OE-Core][PATCH 1/4] rust: Move RUST_DIST_SERVER to rust-config.inc Alex Kiernan
2023-12-30 15:49 ` [OE-Core][PATCH 2/4] cargo: Create CARGO_HOME and CARGO_VENDORING_DIRECTORY Alex Kiernan
2023-12-30 15:49 ` [OE-Core][PATCH 3/4] cargo: Move vendor directory to registry/src Alex Kiernan
2023-12-30 23:46   ` Richard Purdie
2023-12-30 15:49 ` [OE-Core][PATCH 4/4] rust: Upgrade 1.74.1 -> 1.75.0 Alex Kiernan
2023-12-31 14:23   ` Richard Purdie
2023-12-31 14:34     ` Alex Kiernan
     [not found]     ` <17A5F1406166801F.18542@lists.openembedded.org>
2024-01-02  9:24       ` Alex Kiernan
2024-01-11 14:54         ` Sundeep KOKKONDA [this message]
2024-01-14  8:59           ` [OE-core] [PATCH " Alex Kiernan
     [not found]           ` <17AA2B18BB6DAD55.13033@lists.openembedded.org>
2024-02-10 12:03             ` Alex Kiernan
2024-02-11  2:30               ` Sundeep KOKKONDA

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=26286.1704984874999023341@lists.openembedded.org \
    --to=sundeep.kokkonda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox