From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: dlaor@redhat.com
Cc: Juan Quintela <quintela@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Alon Levy <alevy@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
Adam Litke <agl@us.ibm.com>, Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] QEMU: Discussion of separating core functionality vs supportive features
Date: Wed, 02 Mar 2011 11:47:53 +0100 [thread overview]
Message-ID: <4D6E2059.8040603@redhat.com> (raw)
In-Reply-To: <4D6E1F14.5050302@redhat.com>
On 03/02/11 11:42, Dor Laor wrote:
> On 03/02/2011 12:28 PM, Jes Sorensen wrote:
>> On 03/01/11 15:25, Dor Laor wrote:
>>> I agree it is desirable to the this for spice but it is allot more
>>> complex than virtagent isolation. Spice is performance sensitive and
>>> contains much more state. It needs to access the guest memory for
>>> reading the surfaces. It can be solved but needs some major changes.
>>> Adding spice-devel to the discussion.
>>
>> Please don't add broken misconfigured mailing lists, which require
>> moderator or subscription, to discussions on public lists.
>
> Isn't it simpler to ask the spice list maintainer (Alon Levy, CCed) to
> do it?
We cannot have a discussion on a mailing list if we constantly have to
wait for the list maintainer to approve it. There is really zero
justification for closing a development list of an open source project.
Spam is handled in other ways, this doesn't solve it.
Cheers,
Jes
next prev parent reply other threads:[~2011-03-02 10:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 16:42 [Qemu-devel] QEMU: Discussion of separating core functionality vs supportive features Jes Sorensen
2011-02-28 17:44 ` Anthony Liguori
2011-03-01 12:07 ` Dor Laor
2011-03-01 12:40 ` Anthony Liguori
2011-03-01 14:25 ` Dor Laor
2011-03-01 14:29 ` Anthony Liguori
2011-03-02 10:25 ` Jes Sorensen
2011-03-02 10:56 ` Dor Laor
2011-03-02 11:02 ` Jes Sorensen
2011-03-02 10:58 ` Alon Levy
2011-03-02 11:04 ` Dor Laor
2011-03-02 12:39 ` Alon Levy
2011-04-26 9:14 ` Gerd Hoffmann
2011-04-26 13:15 ` Anthony Liguori
2011-03-02 11:05 ` Jes Sorensen
2011-03-02 10:28 ` Jes Sorensen
2011-03-02 10:42 ` Dor Laor
2011-03-02 10:47 ` Jes Sorensen [this message]
2011-03-02 10:21 ` Jes Sorensen
2011-03-02 10:19 ` Jes Sorensen
2011-03-02 13:13 ` Michael Roth
2011-03-02 13:18 ` Jes Sorensen
2011-03-02 13:49 ` Michael Roth
2011-03-03 13:29 ` Jes Sorensen
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=4D6E2059.8040603@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=agl@us.ibm.com \
--cc=alevy@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=amit.shah@redhat.com \
--cc=dlaor@redhat.com \
--cc=kraxel@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.