From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Debian forked, because of systemd brouhaha
Date: Sat, 29 Nov 2014 18:45:48 -0500 [thread overview]
Message-ID: <CAGfcS_k=sKFYB64Ut4CTO8PrAB4A=u6igJ7phK0g9QGByj5b5g@mail.gmail.com> (raw)
In-Reply-To: <547A572B.2000601@marc-stuermer.de>
On Sat, Nov 29, 2014 at 6:30 PM, Marc Stuermer <mail@marc-stuermer.de> wrote:
> That's why I am skeptical about all of this created buzz around it and
> seriously doubt if they are going to be able to deliver.
>
Systemd = buzz these days. There was a slashdot post about some
kernel bug and it seemed like 1/3rd of the posts were talking about
whether systemd is to blame. You can't go three days without some
kind of flamewar, and I'm sure the slashdot marketing team is milking
it for every ad dollar they can get before they go bankrupt... :)
--
Rich
next prev parent reply other threads:[~2014-11-29 23:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 10:11 [gentoo-user] Debian forked, because of systemd brouhaha Pandu Poluan
2014-11-29 11:02 ` Neil Bothwick
2014-11-29 12:15 ` the
2014-11-29 16:32 ` Marc Stürmer
2014-11-30 4:43 ` Andrew Savchenko
2014-12-01 2:54 ` [gentoo-user] " »Q«
2014-12-01 8:22 ` Pandu Poluan
2014-12-01 8:36 ` Marc Stürmer
2014-11-29 23:30 ` [gentoo-user] " Marc Stuermer
2014-11-29 23:45 ` Rich Freeman [this message]
2014-11-30 2:01 ` Bill Kenworthy
2014-11-30 3:32 ` Rich Freeman
2014-11-30 4:35 ` Andrew Savchenko
2014-11-30 12:10 ` Bill Kenworthy
2014-11-30 10:07 ` Marc Stürmer
2014-11-30 11:44 ` Philip Webb
2014-11-30 12:29 ` Marc Stürmer
2014-11-30 13:01 ` Mick
2014-11-30 13:13 ` Neil Bothwick
2014-11-30 16:33 ` Mick
2014-11-30 19:40 ` Neil Bothwick
2014-11-30 16:39 ` Daniel Frey
2014-11-30 17:14 ` Marc Stürmer
2014-12-01 11:54 ` Joerg Schilling
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='CAGfcS_k=sKFYB64Ut4CTO8PrAB4A=u6igJ7phK0g9QGByj5b5g@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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