From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
kvm@vger.kernel.org, "Juan Quintela" <quintela@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-block@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH 00/10] python: Explicit usage of Python 3
Date: Thu, 30 Jan 2020 16:04:05 +0100 [thread overview]
Message-ID: <c90ce40e-428a-ed5e-531f-b2ca99121dfc@redhat.com> (raw)
In-Reply-To: <0a858225-685d-3ffd-845c-6c1f8a438307@virtuozzo.com>
On 1/30/20 3:02 PM, Vladimir Sementsov-Ogievskiy wrote:
> First, thanks for handling this!
>
> 30.01.2020 2:13, Philippe Mathieu-Daudé wrote:
>> Hello,
>>
>> These are mechanical sed patches used to convert the
>> code base to Python 3, as suggested on this thread:
>> https://www.mail-archive.com/qemu-devel@nongnu.org/msg675024.html
>>
>> Regards,
>>
>> Phil.
>>
>> Philippe Mathieu-Daudé (10):
>> scripts: Explicit usage of Python 3
>> tests/qemu-iotests: Explicit usage of Python 3
>> tests: Explicit usage of Python 3
>> scripts/minikconf: Explicit usage of Python 3
>> tests/acceptance: Remove shebang header
>> scripts/tracetool: Remove shebang header
>> tests/vm: Remove shebang header
>> tests/qemu-iotests: Explicit usage of Python 3
>> scripts: Explicit usage of Python 3
>> tests/qemu-iotests/check: Update to match Python 3 interpreter
>>
>
> Could you please not use same subject for different patches? Such things
> are hard to manage during patch porting from version to version.
I can change but I'm not understanding what you want.
>
> Also, will you update checkpatch.pl, to avoid appearing unversioned
> python again?
I'm not sure I can because checkpatch.pl is written in Perl, but I'll try.
next prev parent reply other threads:[~2020-01-30 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 23:13 [PATCH 00/10] python: Explicit usage of Python 3 Philippe Mathieu-Daudé
2020-01-29 23:13 ` [PATCH 01/10] scripts: " Philippe Mathieu-Daudé
2020-01-30 9:13 ` Juan Quintela
2020-01-29 23:13 ` [PATCH 02/10] tests/qemu-iotests: " Philippe Mathieu-Daudé
2020-01-29 23:13 ` [PATCH 03/10] tests: " Philippe Mathieu-Daudé
2020-01-29 23:13 ` [PATCH 04/10] scripts/minikconf: " Philippe Mathieu-Daudé
2020-01-29 23:13 ` [PATCH 05/10] tests/acceptance: Remove shebang header Philippe Mathieu-Daudé
2020-01-30 14:34 ` Wainer dos Santos Moschetta
2020-01-29 23:13 ` [PATCH 06/10] scripts/tracetool: " Philippe Mathieu-Daudé
2020-01-29 23:13 ` [PATCH 07/10] tests/vm: " Philippe Mathieu-Daudé
2020-01-29 23:14 ` [PATCH 08/10] tests/qemu-iotests: Explicit usage of Python 3 Philippe Mathieu-Daudé
2020-01-29 23:14 ` [PATCH 09/10] scripts: " Philippe Mathieu-Daudé
2020-01-29 23:14 ` [PATCH 10/10] tests/qemu-iotests/check: Update to match Python 3 interpreter Philippe Mathieu-Daudé
2020-01-30 10:58 ` Kevin Wolf
2020-01-30 13:34 ` Philippe Mathieu-Daudé
2020-01-30 14:02 ` [PATCH 00/10] python: Explicit usage of Python 3 Vladimir Sementsov-Ogievskiy
2020-01-30 15:04 ` Philippe Mathieu-Daudé [this message]
2020-01-30 15:29 ` Vladimir Sementsov-Ogievskiy
2020-01-30 16:18 ` 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=c90ce40e-428a-ed5e-531f-b2ca99121dfc@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).