From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Petr Kubizňák - 2N" <Kubiznak@2n.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v4 06/10] webkitgtk: add missing dependencies
Date: Mon, 03 Apr 2023 11:43:40 +0100 [thread overview]
Message-ID: <0e3a9766a809aa9b5c933932e28124c9fd7dcc47.camel@linuxfoundation.org> (raw)
In-Reply-To: <DB4PR02MB100301B77BF93E3A3CC6708A5E2929@DB4PR02MB10030.eurprd02.prod.outlook.com>
On Mon, 2023-04-03 at 10:31 +0000, Petr Kubizňák - 2N wrote:
> Hi Richard,
>
> Yes, that is sufficient. I've prepared an updated patch. In the
> meantime, I've noticed some of the patches from the series had been
> merged into master-next, but not to the master yet. Should I now
> resend the whole series, or filter out these patches, i.e. rebase to
> master or master-next?
Normally I'd suggest rebasing on master unless there is another series
this series depends upon. The ones in master-next were the ones I
thought were simpler/ready and had been through testing in that branch.
I've just gone ahead and merged them so you should find they drop out
naturally now.
I sometimes do this just to reduce the need to resend patches, for me
to re-read/re-test them and make it clearer where the review is still
needed.
Cheers,
Richard
next prev parent reply other threads:[~2023-04-03 10:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 11:46 [OE-core][PATCH v4 01/10] gobject-introspection: reduce dependencies Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 02/10] graphene: add gobject-types PACKAGECONFIG Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 03/10] python3-pygobject: depend on gobject-introspection Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 04/10] gconf: add missing dependencies Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 05/10] avahi: " Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 06/10] webkitgtk: " Petr Kubizňák
2023-03-31 12:06 ` Richard Purdie
2023-04-03 10:31 ` Petr Kubizňák - 2N
2023-04-03 10:43 ` Richard Purdie [this message]
2023-03-31 11:46 ` [OE-core][PATCH v4 07/10] harfbuzz: depend on glib-2.0-native Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 08/10] json-glib: " Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 09/10] libgudev: " Petr Kubizňák
2023-03-31 11:46 ` [OE-core][PATCH v4 10/10] at-spi2-core: " Petr Kubizňák
2023-04-03 20:14 ` [OE-core][PATCH v4 01/10] gobject-introspection: reduce dependencies Richard Purdie
2023-04-04 7:07 ` Petr Kubizňák - 2N
2023-04-05 7:05 ` Petr Kubizňák - 2N
2023-04-05 8:19 ` Richard Purdie
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=0e3a9766a809aa9b5c933932e28124c9fd7dcc47.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Kubiznak@2n.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