From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Maydell' <peter.maydell@linaro.org>,
'QEMU Developers' <qemu-devel@nongnu.org>
Cc: "'Edgar E. Iglesias'" <edgar.iglesias@gmail.com>,
"'Peter Crosthwaite'" <crosthwaitepeter@gmail.com>,
"'Alex Bennée'" <alex.bennee@linaro.org>,
"'Paolo Bonzini'" <pbonzini@redhat.com>
Subject: RE: [Qemu-devel] proposal: new qemu-arm mailing list
Date: Tue, 27 Oct 2015 14:07:38 +0300 [thread overview]
Message-ID: <012d01d110a7$b1915690$14b403b0$@samsung.com> (raw)
In-Reply-To: <CAFEAcA-s_hSQiLCkQDeX2rR12PcPx5yZ885yZy7C=ZWA5DDbTw@mail.gmail.com>
Hello!
> The idea would be to get people to cc the
> list with their ARM related patches, so it would mostly act as
> a way for people to filter their mail to separate the ARM stuff
> out from the qemu-devel firehose.
I also vote for it. The main qemu-devel traffic is quite high, and not everyone wants to get it.
> (Everything should still be cc'd to qemu-devel as well.)
I would drop this requirement, except for stuff which could touch core functionality (qom, qobject).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Maydell' <peter.maydell@linaro.org>,
'QEMU Developers' <qemu-devel@nongnu.org>
Cc: "'Edgar E. Iglesias'" <edgar.iglesias@gmail.com>,
"'Peter Crosthwaite'" <crosthwaitepeter@gmail.com>,
"'Alex Bennée'" <alex.bennee@linaro.org>,
"'Paolo Bonzini'" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] proposal: new qemu-arm mailing list
Date: Tue, 27 Oct 2015 14:07:38 +0300 [thread overview]
Message-ID: <012d01d110a7$b1915690$14b403b0$@samsung.com> (raw)
In-Reply-To: <CAFEAcA-s_hSQiLCkQDeX2rR12PcPx5yZ885yZy7C=ZWA5DDbTw@mail.gmail.com>
Hello!
> The idea would be to get people to cc the
> list with their ARM related patches, so it would mostly act as
> a way for people to filter their mail to separate the ARM stuff
> out from the qemu-devel firehose.
I also vote for it. The main qemu-devel traffic is quite high, and not everyone wants to get it.
> (Everything should still be cc'd to qemu-devel as well.)
I would drop this requirement, except for stuff which could touch core functionality (qom, qobject).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-27 11:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 10:15 proposal: new qemu-arm mailing list Peter Maydell
2015-10-27 10:15 ` [Qemu-devel] " Peter Maydell
2015-10-27 10:53 ` Andrew Jones
2015-10-27 10:53 ` Andrew Jones
2015-10-29 15:11 ` Alex Bennée
2015-10-29 15:11 ` Alex Bennée
2015-10-27 11:02 ` Edgar E. Iglesias
2015-10-27 11:02 ` [Qemu-devel] " Edgar E. Iglesias
2015-10-27 15:13 ` Peter Crosthwaite
2015-10-27 15:13 ` [Qemu-devel] " Peter Crosthwaite
2015-10-29 3:51 ` Shannon Zhao
2015-10-29 9:43 ` Sergey Fedorov
2015-10-27 11:07 ` Pavel Fedin [this message]
2015-10-27 11:07 ` Pavel Fedin
2015-10-27 11:16 ` Peter Maydell
2015-10-27 11:16 ` Peter Maydell
2015-10-27 16:59 ` John Snow
2015-10-28 6:49 ` Pavel Fedin
2015-10-28 6:49 ` Pavel Fedin
2015-10-28 15:20 ` John Snow
2015-10-29 14:18 ` Peter Maydell
2015-10-29 14:18 ` [Qemu-devel] " 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='012d01d110a7$b1915690$14b403b0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=alex.bennee@linaro.org \
--cc=crosthwaitepeter@gmail.com \
--cc=edgar.iglesias@gmail.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 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.