From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Zhou, Li" <li.zhou@windriver.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] python2/3: Move config/Makefile from core package to dev package
Date: Tue, 11 Apr 2017 08:20:05 +0100 [thread overview]
Message-ID: <1491895205.12091.4.camel@linuxfoundation.org> (raw)
In-Reply-To: <93eb1af8-d13b-e283-003c-409d2938c781@windriver.com>
Hi,
On Tue, 2017-04-11 at 13:31 +0800, Zhou, Li wrote:
> From the mails I received, I think you have merged the 1st
> version of this patch, while I have sent out the 2nd version for
> fixing the issue mentioned by Jussi .
> I just sent this patch in an accessory, because there are lines which
> are too long to pass the auto tests (but they shouldn't be changed).
> So, please take a look at my 2nd patch in the accessory. Thank you.
Thanks for pointing that out, I've updated the version in -next.
Cheers,
Richard
prev parent reply other threads:[~2017-04-11 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 7:10 [PATCH] python2/3: Move config/Makefile from core package to dev package Li Zhou
2017-04-10 7:31 ` ✗ patchtest: failure for " Patchwork
2017-04-10 8:08 ` [PATCH] " Jussi Kukkonen
2017-04-10 9:25 ` [PATCH V2] " Zhou, Li
2017-04-11 5:31 ` Zhou, Li
2017-04-11 7:20 ` Richard Purdie [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=1491895205.12091.4.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=li.zhou@windriver.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