From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: Re: mem-event interface
Date: Thu, 24 Jun 2010 12:09:07 +0100 [thread overview]
Message-ID: <4C233CD3.8020407@eu.citrix.com> (raw)
In-Reply-To: <63802654-4534-4139-b380-89d341e32864@default>
On 24/06/10 00:12, Dan Magenheimer wrote:
> The page sharing code was added very quickly to xen-unstable
> last year without (afaict) much review or iteration,
> so there's probably other developers that could use some
> additional background. I appreciate that you are
> moving this phase into open discussion!
It's very easy for those of us in Citrix or connected to Citrix (i.e.,
the Cambridge or UBC computer labs) to make design decisions in off-list
discussions, effectively presenting them to the list as nearly finished
designs, with little opportunity for community involvement.
I think we all recognize that this is Not A Good Thing (TM), so I think
if other community members outside the Citrix connections notice this,
please feel free to remind us to be more open with discussions. :-)
-George
next prev parent reply other threads:[~2010-06-24 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinovEV47G8aIw-Na_iQhELjUG3R7VUlAzf1mD66@mail.gmail.com>
2010-06-23 22:19 ` mem-event interface Grzegorz Milos
2010-06-23 22:21 ` Grzegorz Milos
2010-06-23 22:21 ` Grzegorz Milos
2010-06-23 22:22 ` Grzegorz Milos
2010-06-23 22:22 ` Grzegorz Milos
2010-06-23 22:23 ` Grzegorz Milos
2010-06-23 22:23 ` Grzegorz Milos
2010-06-23 22:24 ` Grzegorz Milos
2010-06-23 22:24 ` Grzegorz Milos
2010-06-23 22:25 ` Grzegorz Milos
2010-06-23 22:25 ` Grzegorz Milos
2010-06-24 9:18 ` Tim Deegan
2010-06-27 15:45 ` Grzegorz Milos
2010-06-27 17:40 ` Patrick Colp
2010-06-28 3:12 ` Dan Magenheimer
2010-06-28 9:28 ` Tim Deegan
2010-06-23 23:12 ` Dan Magenheimer
2010-06-24 9:26 ` Tim Deegan
2010-06-24 11:09 ` George Dunlap [this message]
2010-06-27 15:30 ` Grzegorz Milos
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=4C233CD3.8020407@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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.