Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@intel.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] runqemu: formatting cleanups suggested by PyLint
Date: Sat, 15 Dec 2018 11:55:00 +0000	[thread overview]
Message-ID: <3de0daf6d2af873d18c4e8a650be961038d856ff.camel@linuxfoundation.org> (raw)
In-Reply-To: <20181214171034.1897-1-ross.burton@intel.com>

On Fri, 2018-12-14 at 17:10 +0000, Ross Burton wrote:
> Mostly whitespace fixes but also some r"" strings to clarify regular
> expressions.
> 
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
>  meta/lib/oe/package_manager.py | 97 +++++++++++++++++---------------
> ----------
>  scripts/runqemu                | 46 ++++++++++----------
>  2 files changed, 61 insertions(+), 82 deletions(-)

I think your patches got a little confused!

(2 files, not 1)

Cheers,

Richard



      parent reply	other threads:[~2018-12-15 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 17:10 [PATCH] runqemu: formatting cleanups suggested by PyLint Ross Burton
2018-12-14 17:52 ` ✗ patchtest: failure for " Patchwork
2018-12-15 11:55 ` 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=3de0daf6d2af873d18c4e8a650be961038d856ff.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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