From: Gleb Natapov <gleb@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Avi Kivity <avi@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Pekka Enberg <penberg@kernel.org>,
linux-kernel@vger.kernel.org, aarcange@redhat.com,
mtosatti@redhat.com, kvm@vger.kernel.org, joro@8bytes.org,
penberg@cs.helsinki.fi, asias.hejun@gmail.com,
gorcunov@gmail.com
Subject: Re: [ANNOUNCE] Native Linux KVM tool
Date: Wed, 6 Apr 2011 12:51:44 +0300 [thread overview]
Message-ID: <20110406095144.GF25626@redhat.com> (raw)
In-Reply-To: <20110406094612.GA19943@elte.hu>
On Wed, Apr 06, 2011 at 11:46:12AM +0200, Ingo Molnar wrote:
>
> * Gleb Natapov <gleb@redhat.com> wrote:
>
> > On Wed, Apr 06, 2011 at 11:33:33AM +0200, Ingo Molnar wrote:
> >
> > > So no, your kind of cynical, defeatist sentiment about code quality is by
> > > no means true in my experience. Projects become ugly gooballs once
> > > maintainers stop caring enough.
> >
> > In case of Qemu it was other way around. Maintainers started caring too late.
>
> Nah, i do not think it's ever too late to care.
>
> Example: arch/i386 - arch/x86_64/ was very messy for many, many years and we
> turned it around and can be proud of arch/x86/ today - but i guess i'm somewhat
> biased there ;-)
>
> In my experience it's entirely possible to turn a messy gooball into something
> you can be proud of - it's all reversible. Start small, with the core bits you
> care about most - then extend those concepts to other areas of the code base,
> gradually. There might be subsystems that will never turn around before
> becoming obsolete - that's not a big problem.
>
I do not disagree, but then qemu has a chance because maintainers do
care now, but not about all bits. And there should be willingness to
drop bits nobody cares about and I do not see this yet.
--
Gleb.
next prev parent reply other threads:[~2011-04-06 9:52 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 17:30 [ANNOUNCE] Native Linux KVM tool Pekka Enberg
[not found] ` <1B1AE097-4524-4026-85EC-F9A0E274FFF2@suse.de>
2011-04-01 7:07 ` Carsten Otte
2011-04-01 7:37 ` Cyrill Gorcunov
2011-04-01 14:26 ` Steven Rostedt
2011-04-02 20:38 ` Anthony Liguori
2011-04-03 6:21 ` Ingo Molnar
2011-04-03 8:24 ` Avi Kivity
2011-04-03 8:53 ` Pekka Enberg
2011-04-03 9:06 ` Cyrill Gorcunov
2011-04-03 9:37 ` CaT
2011-04-04 10:31 ` Ingo Molnar
2011-04-03 8:51 ` Pekka Enberg
2011-04-03 9:17 ` Avi Kivity
2011-04-03 8:23 ` Avi Kivity
2011-04-03 9:59 ` Pekka Enberg
2011-04-03 10:11 ` Avi Kivity
2011-04-03 10:17 ` Pekka Enberg
2011-04-03 10:22 ` Avi Kivity
2011-04-03 10:32 ` Pekka Enberg
2011-04-03 13:09 ` Anthony Liguori
2011-04-03 13:19 ` Avi Kivity
2011-04-06 9:33 ` Ingo Molnar
2011-04-06 9:36 ` Gleb Natapov
2011-04-06 9:46 ` Ingo Molnar
2011-04-06 9:49 ` Avi Kivity
2011-04-06 9:51 ` Gleb Natapov [this message]
2011-04-06 10:14 ` Olivier Galibert
2011-04-06 10:55 ` Ingo Molnar
2011-04-08 2:04 ` Anthony Liguori
2011-04-08 2:14 ` Anthony Liguori
2011-04-08 5:14 ` Pekka Enberg
2011-04-08 6:19 ` Cyrill Gorcunov
2011-04-08 6:47 ` Takuya Yoshikawa
2011-04-08 6:51 ` Pekka Enberg
2011-04-08 7:10 ` Takuya Yoshikawa
2011-04-08 7:39 ` Jan Kiszka
2011-04-08 8:27 ` Pekka Enberg
2011-04-08 9:11 ` Jan Kiszka
2011-04-08 9:32 ` Cyrill Gorcunov
2011-04-08 10:42 ` Jan Kiszka
2011-04-08 12:27 ` Alexander Graf
2011-04-08 12:33 ` Cyrill Gorcunov
2011-04-08 14:39 ` Ted Ts'o
2011-04-08 14:00 ` Anthony Liguori
2011-04-08 19:20 ` Andrea Arcangeli
2011-04-08 22:59 ` Anthony Liguori
2011-04-10 8:05 ` Avi Kivity
2011-04-09 7:40 ` Ingo Molnar
2011-04-12 0:58 ` Andrea Arcangeli
2011-04-09 18:23 ` Olivier Galibert
2011-04-10 2:54 ` Anthony Liguori
2011-04-08 15:59 ` Scott Wood
2011-04-08 19:41 ` gene heskett
2011-04-08 22:58 ` Anthony Liguori
2011-04-06 8:59 ` Markus Armbruster
2011-04-06 9:29 ` Gleb Natapov
2011-04-03 9:01 ` Alon Levy
2011-04-03 10:01 ` Pekka Enberg
2011-04-03 10:15 ` Alon Levy
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=20110406095144.GF25626@redhat.com \
--to=gleb@redhat.com \
--cc=aarcange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=penberg@kernel.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