From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, chugh.ishani@research.iiit.ac.in, famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] scripts: add argparse module for Python 2.6 compatibility
Date: Tue, 29 Aug 2017 10:59:37 +0100 [thread overview]
Message-ID: <20170829095937.GM25960@stefanha-x1.localdomain> (raw)
In-Reply-To: <150367827575.135.18312492625326080794@205a2245145f>
On Fri, Aug 25, 2017 at 09:24:36AM -0700, no-reply@patchew.org wrote:
> === OUTPUT BEGIN ===
> Checking PATCH 1/3: scripts: add argparse module for Python 2.6 compatibility...
> ERROR: trailing whitespace
> #115: FILE: COPYING.PYTHON:93:
> +Reserved" are retained in Python alone or in any derivative version $
>
> total: 1 errors, 0 warnings, 2676 lines checked
I'm not going to modify the Python Software Foundation License text for
the sake of checkpatch.pl. Let's keep it verbatim.
next prev parent reply other threads:[~2017-08-29 9:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 15:57 [Qemu-devel] [PATCH 0/3] scripts: add argparse module for Python 2.6 compatibility Stefan Hajnoczi
2017-08-25 15:57 ` [Qemu-devel] [PATCH 1/3] " Stefan Hajnoczi
2017-08-25 15:57 ` [Qemu-devel] [PATCH 2/3] docker.py: Python 2.6 argparse compatibility Stefan Hajnoczi
2017-08-26 0:29 ` Fam Zheng
2017-08-25 15:57 ` [Qemu-devel] [PATCH 3/3] tests: migration/guestperf " Stefan Hajnoczi
2017-08-25 16:24 ` [Qemu-devel] [PATCH 0/3] scripts: add argparse module for Python 2.6 compatibility no-reply
2017-08-29 9:59 ` Stefan Hajnoczi [this message]
2017-08-25 16:35 ` Philippe Mathieu-Daudé
2017-08-25 16:40 ` Peter Maydell
2017-08-25 17:42 ` Eric Blake
2017-08-29 10:01 ` Stefan Hajnoczi
2017-08-29 18:02 ` Philippe Mathieu-Daudé
2017-08-28 21:47 ` John Snow
2017-08-30 11:02 ` Stefan Hajnoczi
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=20170829095937.GM25960@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=chugh.ishani@research.iiit.ac.in \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.