[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r3p1ar0c.fsf@x220.int.ebiederm.org>
Date: Wed, 24 Jun 2015 13:41:07 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: David Lang <david@...g.hm>
Cc: Ingo Molnar <mingo@...nel.org>,
Martin Steigerwald <martin@...htvoll.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
David Herrmann <dh.herrmann@...il.com>,
Djalal Harouni <tixxdz@...ndz.org>,
Greg KH <gregkh@...uxfoundation.org>,
Havoc Pennington <havoc.pennington@...il.com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tom Gundersen <teg@...m.no>, Daniel Mack <daniel@...que.org>
Subject: Re: kdbus: to merge or not to merge?
David Lang <david@...g.hm> writes:
> On Wed, 24 Jun 2015, Ingo Molnar wrote:
>
>> And the thing is, in hindsight, after such huge flamewars, years down the line,
>> almost never do I see the following question asked: 'what were we thinking merging
>> that crap??'. If any question arises it's usually along the lines of: 'what was
>> the big fuss about?'. So I think by and large the process works.
>
> counterexamples, devfs, tux
The biggest I can think of cgroups.
The way cgroups connect to processes instead of resources (semantically)
and the fact that controllers are different from fundamental entities
like schedulers.
Of course I don't think "What were we thinking" I remember it all too
well in that case.
I think "What do we do now that we have made this mess".
Eric
--
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