From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Ross Burton <ross.burton@arm.com>
Cc: "wangmy@fujitsu.com" <wangmy@fujitsu.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] pango: upgrade 1.50.10 -> 1.50.11
Date: Thu, 13 Oct 2022 09:30:17 +0200 [thread overview]
Message-ID: <Y0e+ifOc5Wq4ortM@mail.local> (raw)
In-Reply-To: <D47A4D61-C059-4AE3-A08F-89D4BC7F429B@arm.com>
On 12/10/2022 16:46:44+0000, Ross Burton wrote:
> We only have 1.50.9 in oe-core master, please ensure that you sent patches based on master, or if they’re based on another staging branch please make that clear.
>
this applied fine on master-next because we carry your 1.50.10 upgrade
> Ross
>
> > On 11 Oct 2022, at 09:05, wangmy via lists.openembedded.org <wangmy=fujitsu.com@lists.openembedded.org> wrote:
> >
> > Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> > ---
> > .../pango/{pango_1.50.10.bb => pango_1.50.11.bb} | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > rename meta/recipes-graphics/pango/{pango_1.50.10.bb => pango_1.50.11.bb} (94%)
> >
> > diff --git a/meta/recipes-graphics/pango/pango_1.50.10.bb b/meta/recipes-graphics/pango/pango_1.50.11.bb
> > similarity index 94%
> > rename from meta/recipes-graphics/pango/pango_1.50.10.bb
> > rename to meta/recipes-graphics/pango/pango_1.50.11.bb
> > index 95209889a8..1120e053b8 100644
> > --- a/meta/recipes-graphics/pango/pango_1.50.10.bb
> > +++ b/meta/recipes-graphics/pango/pango_1.50.11.bb
> > @@ -24,7 +24,7 @@ SRC_URI += "file://run-ptest \
> > file://0001-Skip-running-test-layout-test.patch \
> > "
> >
> > -SRC_URI[archive.sha256sum] = "7e5d2f1e40854d24a9a2c4d093bafe75dcdbeccdf1de43e4437332eabed64966"
> > +SRC_URI[archive.sha256sum] = "8800f812d89ee61388188703203f3a7878963c22f8695aaf1fa0a1a1428d17ae"
> >
> > DEPENDS = "glib-2.0 glib-2.0-native fontconfig freetype virtual/libiconv cairo harfbuzz fribidi"
> >
> > --
> > 2.25.1
> >
> >
> >
> >
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#171672): https://lists.openembedded.org/g/openembedded-core/message/171672
> Mute This Topic: https://lists.openembedded.org/mt/94254215/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-10-13 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 8:05 [OE-core] [PATCH] libffi: upgrade 3.4.2 -> 3.4.3 Wang Mingyu
2022-10-11 8:05 ` [OE-core] [PATCH] libva: upgrade 2.15.0 -> 2.16.0 Wang Mingyu
2022-10-11 8:05 ` [OE-core] [PATCH] libva-utils: " Wang Mingyu
2022-10-11 8:05 ` [OE-core] [PATCH] pango: upgrade 1.50.10 -> 1.50.11 Wang Mingyu
2022-10-12 16:46 ` Ross Burton
2022-10-13 7:30 ` Alexandre Belloni [this message]
2022-10-13 7:31 ` Alexandre Belloni
2022-10-11 8:05 ` [OE-core] [PATCH] powertop: upgrade 2.14 -> 2.15 Wang Mingyu
2022-10-11 14:06 ` [OE-core] [PATCH] libffi: upgrade 3.4.2 -> 3.4.3 Alexandre Belloni
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=Y0e+ifOc5Wq4ortM@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=wangmy@fujitsu.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