From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ming Liu <liu.ming50@gmail.com>
Cc: Ming Liu <peter.x.liu@external.atlascopco.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS
Date: Wed, 23 Aug 2017 08:59:57 +0100 [thread overview]
Message-ID: <1503475197.32591.140.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALatG=6NOefmTqj-1OatYNH+43Bpwzo0Xz+BdrMYrYjZMkJTkw@mail.gmail.com>
On Wed, 2017-08-23 at 09:57 +0200, Ming Liu wrote:
> Yes, it's in master-next not in master branch, but wouldn't that mean
> it's accepted as a proper fix, or?
It means it was queued for testing, I've dropped it from master-next
now as the comments from Chris still apply from last time.
Cheers,
Richard
next prev parent reply other threads:[~2017-08-23 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 11:43 [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS liu.ming50
2017-08-23 2:19 ` Andre McCurdy
2017-08-23 2:33 ` Ming Liu
2017-08-23 7:50 ` Richard Purdie
2017-08-23 7:57 ` Ming Liu
2017-08-23 7:59 ` Richard Purdie [this message]
2017-08-23 8:10 ` Ming Liu
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=1503475197.32591.140.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liu.ming50@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.x.liu@external.atlascopco.com \
/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