public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ross.burton@arm.com,
	"Divya.Chellam@windriver.com" <Divya.Chellam@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] python3: Upgrade 3.12.5 -> 3.12.6
Date: Thu, 12 Sep 2024 22:26:06 +0100	[thread overview]
Message-ID: <406bd3f38590ea10fd54a0cfbc6d17a748897020.camel@linuxfoundation.org> (raw)
In-Reply-To: <8940EC00-1BE1-429E-AFE7-D250C9196351@arm.com>

On Thu, 2024-09-12 at 17:43 +0000, Ross Burton via
lists.openembedded.org wrote:
> Hi Divya,
> 
> > On 12 Sep 2024, at 16:22, Richard Purdie via lists.openembedded.org
> > <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
> > Unfortunately "0001-test_readline-skip-limited-history-test.patch"
> > is still needed as it failed in testing:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6985/steps/12/logs/stdio
> > 
> > Could you rebase that patch and resend with it included please?
> 
> We’d really like this to be part of the next release which is
> scheduled to be built asap (like, Monday), so sending this revised
> patch promptly would be _much_ appreciated.

As I'm worried about time pressures, I've tried refreshing that patch
in master-next and am retesting...

Cheers,

Richard


      reply	other threads:[~2024-09-12 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  6:44 [PATCH] python3: Upgrade 3.12.5 -> 3.12.6 dchellam
2024-09-12 15:22 ` [OE-core] " Richard Purdie
2024-09-12 17:43   ` Ross Burton
2024-09-12 21:26     ` Richard Purdie [this message]

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=406bd3f38590ea10fd54a0cfbc6d17a748897020.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Divya.Chellam@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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