From: "Wolber (US), Chuck" <chuck.wolber@boeing.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [EXTERNAL] Re: [OE-core] [PATCH v2] scripts/oe-setup-layers: Make efficiently idempotent
Date: Tue, 17 Jan 2023 17:25:32 +0000 [thread overview]
Message-ID: <82AADBA5-67AA-48AF-A231-DE8EE90CFED4@boeing.com> (raw)
In-Reply-To: <CANNYZj-d-Ref70qgf=+fr8ZDx_KXZ02q36d1Z7Qq4bEF5URAUQ@mail.gmail.com>
On 1/17/23, 9:05 AM, "Alexander Kanavin" <alex.kanavin@gmail.com <mailto: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 <mailto: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.
Agreed, it sounds like RP is holding Alex's patch back, so you should
probably go with my v2. Alex should not have any problems working
against my v2 patch when he updates his own patch.
..Ch:W..
prev parent reply other threads:[~2023-01-17 17:25 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
2023-01-17 17:25 ` Wolber (US), Chuck [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=82AADBA5-67AA-48AF-A231-DE8EE90CFED4@boeing.com \
--to=chuck.wolber@boeing.com \
--cc=alex.kanavin@gmail.com \
--cc=luca.ceresoli@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox