From: Alexander Holler <holler@ahsoftware.de>
To: Borislav Petkov <bp@alien8.de>, Peter Zijlstra <peterz@infradead.org>
Cc: "Måns Rullgård" <mans@mansr.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Christopher Barry" <christopher.r.barry@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: OT: Open letter to the Linux World
Date: Mon, 18 Aug 2014 20:15:45 +0200 [thread overview]
Message-ID: <53F242D1.4050506@ahsoftware.de> (raw)
In-Reply-To: <20140813090013.GA20581@pd.tnic>
Am 13.08.2014 11:00, schrieb Borislav Petkov:
> On Wed, Aug 13, 2014 at 10:27:56AM +0200, Peter Zijlstra wrote:
>> And the thing is; we're all very busy so we tend to take the 'easy'
>> way out for things like this; but wholesale switching all my machines
>> is indeed painful, and I'm not liking.
>
> Right, I think kernel people will gladly jump on a sane solution devoid
> of that kids-jerking-off-on-linux-desktop-just-for-the-fun-of-it
> situation if someone would present them with one. So, if someone would
> come up and do a sane init design without the jerking off, kernel people
> would jump on that in a heartbeat. Someone might even start getting
> patches from them too. ^^Hint^^ ^^hint^^.
>
> :-)
Hmm, a sane and maintainable solution would use C++ with which people
don't have to manually build lists or hashes for every structure like in
the kernel (generic programming done right). So you won't find much
kernel developers there. ;)
Regards,
Alexander Holler
next prev parent reply other threads:[~2014-08-18 20:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 19:38 OT: Open letter to the Linux World Christopher Barry
2014-08-12 20:21 ` Steven Rostedt
2014-08-12 20:44 ` Borislav Petkov
2014-08-12 22:07 ` Måns Rullgård
2014-08-13 8:27 ` Peter Zijlstra
2014-08-13 9:00 ` Borislav Petkov
2014-08-18 18:15 ` Alexander Holler [this message]
2014-09-04 7:54 ` Peter Zijlstra
2014-09-04 10:16 ` Alexander Holler
2014-09-04 14:36 ` Austin S Hemmelgarn
2014-09-04 17:29 ` Alexander Holler
2014-09-04 17:58 ` Austin S Hemmelgarn
2014-09-04 18:11 ` Alexander Holler
2014-09-04 18:27 ` Rogelio Serrano
2014-09-04 18:33 ` Alexander Holler
2014-09-04 19:18 ` Rob Landley
2014-09-05 6:31 ` Alexander Holler
2014-09-06 20:01 ` Alexander Holler
2014-09-06 23:44 ` Lennart Sorensen
2014-09-07 1:42 ` Alexander Holler
2014-08-13 9:24 ` Måns Rullgård
2014-08-13 9:31 ` Peter Zijlstra
2014-08-13 9:37 ` Måns Rullgård
2014-08-13 9:37 ` Martin Steigerwald
2014-08-13 9:52 ` Peter Zijlstra
2014-08-13 9:59 ` Martin Steigerwald
2014-08-13 9:54 ` Peter Zijlstra
2014-08-13 9:57 ` Måns Rullgård
2014-08-13 10:21 ` Martin Steigerwald
2014-08-13 20:19 ` William Pitcock
2014-08-14 1:08 ` Robert Hancock
2014-08-15 18:41 ` Jaswinder Singh
2015-04-08 13:12 ` Denys Vlasenko
2015-04-09 0:37 ` Rob Landley
2015-04-09 18:18 ` Denys Vlasenko
2015-04-10 12:40 ` Rogelio M. Serrano Jr.
2015-04-10 21:20 ` Aaro Koskinen
2015-04-11 1:08 ` Rob Landley
[not found] <E1XHxA6-0000ar-2a@feisty.vs19.net>
2014-08-15 8:59 ` Vlad Glagolev
2014-08-15 14:04 ` Gene Heskett
2014-08-16 21:10 ` Rob Landley
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=53F242D1.4050506@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=bp@alien8.de \
--cc=christopher.r.barry@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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