From: John Snow <jsnow@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>,
'Peter Maydell' <peter.maydell@linaro.org>
Cc: "'Edgar E. Iglesias'" <edgar.iglesias@gmail.com>,
"'Peter Crosthwaite'" <crosthwaitepeter@gmail.com>,
"'Alex Bennée'" <alex.bennee@linaro.org>,
"'QEMU Developers'" <qemu-devel@nongnu.org>,
"'Paolo Bonzini'" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] proposal: new qemu-arm mailing list
Date: Wed, 28 Oct 2015 11:20:31 -0400 [thread overview]
Message-ID: <5630E7BF.8000000@redhat.com> (raw)
In-Reply-To: <008601d1114c$c5fa0aa0$51ee1fe0$@samsung.com>
On 10/28/2015 02:49 AM, Pavel Fedin wrote:
> Hello!
>
>> Just to jump on and bead a dead horse, I am not OK with the idea of a
>> mailing list where patches might get reviewed and staged for pull
>> without the general population of qemu-devel being able to look first.
>
> Ok ok, i don't object, Peter has already explained a similar thing to me, and i silently agreed.
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
Sorry :)
I am of course in favor of the list in general. qemu-block has been very
useful for us.
--js
next prev parent reply other threads:[~2015-10-28 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 10:15 [Qemu-devel] proposal: new qemu-arm mailing list Peter Maydell
2015-10-27 10:53 ` Andrew Jones
2015-10-29 15:11 ` Alex Bennée
2015-10-27 11:02 ` Edgar E. Iglesias
2015-10-27 15:13 ` Peter Crosthwaite
2015-10-29 3:51 ` Shannon Zhao
2015-10-29 9:43 ` Sergey Fedorov
2015-10-27 11:07 ` Pavel Fedin
2015-10-27 11:16 ` Peter Maydell
2015-10-27 16:59 ` John Snow
2015-10-28 6:49 ` Pavel Fedin
2015-10-28 15:20 ` John Snow [this message]
2015-10-29 14:18 ` Peter Maydell
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=5630E7BF.8000000@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosthwaitepeter@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=p.fedin@samsung.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).