From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Marius Kriegerowski <marius.kriegerowski@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [kirkstone][PATCH 1/2] bitbake: bitbake-diffsigs: Make PEP8 compliant
Date: Wed, 8 Feb 2023 13:11:55 +0200 [thread overview]
Message-ID: <Y+ODe9axjto3kA1f@nuoska> (raw)
In-Reply-To: <777dd7c0c335480f82f31f1e1b36b751@axis.com>
Hi,
On Wed, Feb 08, 2023 at 11:00:22AM +0000, Peter Kjellerstedt wrote:
> > -----Original Message-----
> > From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of Mikko Rapeli
> > Sent: den 7 februari 2023 10:50
> > To: openembedded-core@lists.openembedded.org
> > Cc: Marius Kriegerowski <marius.kriegerowski@gmail.com>; Alexandre Belloni <alexandre.belloni@bootlin.com>; Richard Purdie <richard.purdie@linuxfoundation.org>; Mikko Rapeli <mikko.rapeli@linaro.org>
> > Subject: [OE-core] [kirkstone][PATCH 1/2] bitbake: bitbake-diffsigs: Make PEP8 compliant
>
> This should be sent to the bitbake list. Also, when cherry-picking
> Bitbake changes in the poky repository, you should remove the "bitbake:"
> prefix from the subject line as it is added by combo-layer when it
> imports the commits from the bitbake repository to the poky repository.
Thanks, forgot all about this... I guess the version/branches is
different too.
Cheers,
-Mikko
prev parent reply other threads:[~2023-02-08 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 9:50 [kirkstone][PATCH 1/2] bitbake: bitbake-diffsigs: Make PEP8 compliant Mikko Rapeli
2023-02-07 9:50 ` [kirkstone][PATCH 2/2] bitbake: bitbake-diffsigs: break on first dependent task difference Mikko Rapeli
2023-02-08 11:00 ` [OE-core] [kirkstone][PATCH 1/2] bitbake: bitbake-diffsigs: Make PEP8 compliant Peter Kjellerstedt
2023-02-08 11:11 ` Mikko Rapeli [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=Y+ODe9axjto3kA1f@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=marius.kriegerowski@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--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