From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Chuck Wolber <chuck.wolber@boeing.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] scripts/oe-setup-layers: Make efficiently idempotent
Date: Tue, 17 Jan 2023 18:08:42 +0100 [thread overview]
Message-ID: <20230117180842.17b3666a@booty> (raw)
In-Reply-To: <CANNYZj-d-Ref70qgf=+fr8ZDx_KXZ02q36d1Z7Qq4bEF5URAUQ@mail.gmail.com>
Hi Alex,
On Tue, 17 Jan 2023 18:05:12 +0100
"Alexander Kanavin" <alex.kanavin@gmail.com> wrote:
> On Tue, 17 Jan 2023 at 18:03, Luca Ceresoli via lists.openembedded.org
> <luca.ceresoli=bootlin.com@lists.openembedded.org> wrote:
>
> > I'm afraind I am unable to apply this patch on my testing branch as it
> > conflicts with another patch ("oe-setup-build: add a tool for
> > discovering config templates and setting up builds" by Alexander
> > Kanavin) which is already on my branch.
> >
> > You might want to rework your patch on top of Alex's, or just wait for
> > it to be on master and then send a v3.
>
> I think RP is not going to accept the oe-setup-build patch in its
> current form, so you can drop it for now.
Ah, sure, I had missed that, thanks for pointing out!
I removed Alex's patch from my branch and added Chuck's.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-01-17 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 1:59 [PATCH v2] scripts/oe-setup-layers: Make efficiently idempotent Chuck Wolber
2023-01-17 17:03 ` [OE-core] " Luca Ceresoli
2023-01-17 17:05 ` Alexander Kanavin
2023-01-17 17:08 ` Luca Ceresoli [this message]
2023-01-17 17:25 ` [EXTERNAL] " Wolber (US), Chuck
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=20230117180842.17b3666a@booty \
--to=luca.ceresoli@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=chuck.wolber@boeing.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.