[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100318143951.GB23126@redhat.com>
Date: Thu, 18 Mar 2010 10:39:51 -0400
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: John Kacur <jkacur@...hat.com>, Avi Kivity <avi@...hat.com>,
Alexander Graf <agraf@...e.de>,
Anthony Liguori <anthony@...emonkey.ws>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Sheng Yang <sheng@...ux.intel.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
Marcelo Tosatti <mtosatti@...hat.com>,
oerg Roedel <joro@...tes.org>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Gleb Natapov <gleb@...hat.com>,
Zachary Amsden <zamsden@...hat.com>, ziteng.huang@...el.com,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Fr?d?ric Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single project
Hi -
On Thu, Mar 18, 2010 at 03:25:04PM +0100, Ingo Molnar wrote:
> [...]
> > Us guys reading and participating on the list. ;)
>
> I'd like to second that - i'm actually quite happy to update the distro
> kernel. Also, i have rarely any problems even with bleeding edge kernels in
> rawhide - they are working pretty smoothly.
>
> A large xorg update showing up in yum update gives me the cringe though ;-)
>From a parochial point of view, that makes perfect sense: someone
else's large software changes are a source of concern. The same thing
applies to non-LKML people -- ordinary users -- when *your* large
software changes are proposed.
Perhaps this change in perspective would help you see the absurdity of
proposing kernel-2.6.git as a hosting repository for all kinds of
stuff, on the theory that kernel updates get pushed to "eager" users
more frequently than other kinds of updates. (Never mind that data
shows otherwise.)
- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists