All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alex Kiernan <alex.kiernan@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-Core][PATCH v4 00/11] Add rust runtime tests
Date: Mon, 26 Dec 2022 10:27:02 +0000	[thread overview]
Message-ID: <bd340a0b68a4f747103cdd1fc015d2236f839f5f.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAO5Uq5SqpQyL8PQHsFYDn8B7rios5EvpCni_5-JmzksAKWP0tw@mail.gmail.com>

On Mon, 2022-12-26 at 09:41 +0000, Alex Kiernan wrote:
> There's something odd happened here. Three of the patches in the
> previous version I posted look to have been merged in poky, but not
> oe-core? I thought the flow was from oe-core into poky.

I'd attempted to take three of them into master-next to try and move
things along a little with testing. It looks like I've messed something
up. I'll try and reconcile things, thanks for pointing it out. Not sure
how I managed this!

Cheers,

Richard


  reply	other threads:[~2022-12-26 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17342835AC830076.27785@lists.openembedded.org>
2022-12-26  9:41 ` [OE-Core][PATCH v4 00/11] Add rust runtime tests Alex Kiernan
2022-12-26 10:27   ` Richard Purdie [this message]
     [not found]   ` <17345100F004118F.27785@lists.openembedded.org>
2022-12-26 11:15     ` Richard Purdie
2022-12-25 21:59 Alex Kiernan
2022-12-26 18:33 ` Richard Purdie
2022-12-27 18:09   ` Alex Kiernan
2022-12-28  0:00     ` Richard Purdie
2022-12-28 14:51       ` Alex Kiernan
2022-12-29 12:53         ` Richard Purdie
2022-12-29 19:25           ` 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=bd340a0b68a4f747103cdd1fc015d2236f839f5f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kiernan@gmail.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.