xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: lars.kurth@xen.org, George.Dunlap@citrix.com,
	Alex Bligh <alex@alex.org.uk>,
	xen-devel@lists.xen.org
Subject: Re: [Hackathon Minutes] Xen 4.4 Planning
Date: Fri, 14 Jun 2013 10:47:19 +0100	[thread overview]
Message-ID: <51BAE6A7.5010802@eu.citrix.com> (raw)
In-Reply-To: <51BAED4702000078000DE484@nat28.tlf.novell.com>

On 14/06/13 09:15, Jan Beulich wrote:
> But isn't that how open source projects work - everyone contributes
> and fixes bugs. If you don't want to help fixing bugs, I'm afraid
> there's also no good reason for you to complain they don't get fixed.

Well, Jan, that's how the market works -- people use the project that 
has the best code and the least bugs; if people find more stability with 
KVM, then people are likely to switch to it even if they don't think the 
performance or architecture is as good as they want.  It's no good 
complaining that your users aren't helping to fix bugs if there are 
other projects with fewer bugs to fix. :-)

Alex and his team has been very helpful in helping test and track down 
some issues in 4.3, and we really appreciate the effort they've put in.

  -George

  reply	other threads:[~2013-06-14  9:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 14:00 [Hackathon Minutes] Xen 4.4 Planning Lars Kurth
2013-06-13 14:22 ` Jan Beulich
2013-06-13 15:11   ` George Dunlap
2013-06-13 15:30     ` Jan Beulich
2013-06-13 15:39       ` Ian Campbell
2013-06-17  8:27         ` Fabio Fantoni
2013-06-17  9:52           ` Ian Campbell
2013-06-13 14:31 ` Ian Campbell
2013-06-13 14:52   ` George Dunlap
2013-06-13 15:06     ` Ian Campbell
2013-06-14 17:41   ` Konrad Rzeszutek Wilk
2013-06-13 14:43 ` George Dunlap
2013-06-13 17:09 ` Ben Guthro
2013-06-13 18:07   ` Pasi Kärkkäinen
2013-06-13 21:03 ` Alex Bligh
2013-06-13 23:56   ` Ian Murray
2013-06-14  7:01     ` Alex Bligh
2013-06-14  9:46       ` Ian Murray
2013-06-14 11:53         ` Alex Bligh
2013-06-14 12:32           ` Ian Murray
2013-06-14 12:49             ` Alex Bligh
2013-06-14 13:34               ` Ian Murray
2013-06-14 13:55                 ` Ian Campbell
2013-06-14 14:44                   ` Ian Murray
2013-06-14 14:55                     ` Gordan Bobic
2013-06-14 15:00                       ` George Dunlap
2013-06-14 15:09                     ` Ian Campbell
2013-06-14 15:43                   ` Alex Bligh
2013-06-14 21:05                     ` Ian Murray
2013-06-19 21:22                     ` Alex Bligh
2013-06-14 15:44                 ` Alex Bligh
2013-06-14 17:25         ` Konrad Rzeszutek Wilk
2013-06-14  8:15   ` Jan Beulich
2013-06-14  9:47     ` George Dunlap [this message]
2013-06-14  9:59     ` Lars Kurth
2013-06-14 10:45       ` Jan Beulich
2013-06-14 11:19         ` George Dunlap
2013-06-14 11:30         ` Gordan Bobic
2013-06-14 12:10       ` Sander Eikelenboom
2013-06-14 10:44   ` George Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2013-06-14 11:46 Alex Bligh
2013-06-14 12:26 ` Jan Beulich
2013-06-14 12:45   ` Alex Bligh
2013-06-14 18:55 Alex Bligh

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=51BAE6A7.5010802@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=alex@alex.org.uk \
    --cc=lars.kurth@xen.org \
    --cc=xen-devel@lists.xen.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).