From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd and kernel developers cooperating to turn it into a global cgroup manager?
Date: Mon, 21 Oct 2013 06:59:57 -0400 [thread overview]
Message-ID: <5265092D.40608@libertytrek.org> (raw)
In-Reply-To: <CAG2nJkNbdjHdMpR0ur6FT-yqBebdT9_iU40Goref5DBvH4ycDQ@mail.gmail.com>
On 2013-10-21 6:48 AM, Mark David Dumlao <madumlao@gmail.com> wrote:
> Again. This power is overstated and overtrusted. As for "rip it out at
> its roots" he has no ability to do that, only refuse to merge it in
> his tree.
Which I believe is a much bigger deal than you seem to think.
> But that's only if he bothers to read it. With all the other
> stuff he's working on, he signs off less commits than all the other
> maintainers do.
<sigh> irrelevant, because I was talking about something that was
discovered *after* it was merged... obviously, if something is merged
that creates a problem (or loud complaints, or whatever), at *that*
point he will certainly take the time to 'read it' and decide if there
is anything to it...
> The news sites love making a big deal of him flaming this or that
> developer or company, but I can't remember that ever stopping anyone
> from doing what they wanted.
Lol... really? You don't consider him rejecting a patch, whether or not
it is rejected 'nicely' or not - 'stopping' said dev from 'doing what
they wanted (ie, get their patch merged)?
Anyway, it really doesn't matter, so no reason to continue this
discussion...
next prev parent reply other threads:[~2013-10-21 11:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 4:27 [gentoo-user] systemd and kernel developers cooperating to turn it into a global cgroup manager? Mark David Dumlao
2013-10-19 15:02 ` Daniel Campbell
2013-10-19 23:35 ` Volker Armin Hemmann
2013-10-20 6:34 ` Daniel Campbell
2013-10-20 7:37 ` Samuli Suominen
2013-10-20 9:24 ` Daniel Campbell
2013-10-20 9:55 ` Samuli Suominen
2013-10-20 10:47 ` Daniel Campbell
2013-10-20 13:02 ` Samuli Suominen
2013-10-20 14:01 ` Tanstaafl
2013-10-20 14:03 ` Samuli Suominen
2013-10-21 2:34 ` Walter Dnes
2013-10-21 5:31 ` Daniel Campbell
2013-10-21 7:34 ` Samuli Suominen
2013-10-21 7:33 ` Samuli Suominen
2013-10-20 14:05 ` Samuli Suominen
2013-10-23 22:51 ` [gentoo-user] " Steven J. Long
2013-10-24 3:48 ` Daniel Campbell
2013-10-20 9:24 ` [gentoo-user] " Volker Armin Hemmann
2013-10-20 10:52 ` Daniel Campbell
2013-10-20 11:02 ` Volker Armin Hemmann
2013-10-20 11:18 ` Daniel Campbell
2013-10-21 20:33 ` Volker Armin Hemmann
2013-10-22 8:43 ` Daniel Campbell
2013-10-20 14:42 ` Tanstaafl
2013-10-21 1:14 ` Mark David Dumlao
2013-10-21 9:55 ` Tanstaafl
2013-10-21 10:11 ` Mark David Dumlao
2013-10-21 10:27 ` Tanstaafl
2013-10-21 10:48 ` Mark David Dumlao
2013-10-21 10:59 ` Tanstaafl [this message]
2013-10-21 11:10 ` Mark David Dumlao
2013-10-21 11:53 ` Tanstaafl
2013-10-21 20:34 ` Volker Armin Hemmann
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=5265092D.40608@libertytrek.org \
--to=tanstaafl@libertytrek.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