public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trouble on the horizon!
Date: Mon, 24 Sep 2018 20:25:03 +0200	[thread overview]
Message-ID: <22618763.9V1QOtgDSA@eve> (raw)
In-Reply-To: <CAGfcS_nCs0r14ZjpxMQm3AXynzSPVKGMyKN74eoT5X14Ks=iNg@mail.gmail.com>

On Monday, September 24, 2018 2:59:02 PM CEST Rich Freeman wrote:
> On Mon, Sep 24, 2018 at 8:42 AM Philip Webb <purslow@ca.inter.net> wrote:

> > He's  48 yo  & beginning to age a bit & it's no threat to anyone
> > if he's decided to take a break for a few kernel cycles.
> 
> ++  Nobody owns Linus.

Except maybe his wife ;)

> By now the kernel should be at a point where
> others can manage the workflow if he isn't around.

I would assume so.





  parent reply	other threads:[~2018-09-24 18:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  7:02 [gentoo-user] Trouble on the horizon! Alan Grimes
2018-09-24  9:00 ` Adam Carter
2018-09-24  9:01 ` [gentoo-user] " Nikos Chantziaras
2018-09-24 10:11   ` R0b0t1
2018-09-24 10:33     ` Nikos Chantziaras
2018-09-24 11:39       ` R0b0t1
2018-09-25  4:49       ` Mark David Dumlao
2018-09-25 20:26         ` Wols Lists
2018-09-24 12:42 ` [gentoo-user] " Philip Webb
2018-09-24 12:59   ` Rich Freeman
2018-09-24 16:27     ` Jack
2018-09-24 18:25     ` J. Roeleveld [this message]
2018-09-24 18:24   ` J. Roeleveld
2018-09-24 22:55     ` [gentoo-user] Re : kernel delay Philip Webb
2018-09-25  7:34       ` Peter Humphrey
2018-10-04  9:35         ` [gentoo-user] [Even further OT] " Peter Humphrey
2018-09-25  4:36     ` [gentoo-user] Trouble on the horizon! gevisz
2018-09-25  6:14       ` J. Roeleveld
2018-09-25  6:23         ` gevisz
2018-09-25  7:12           ` J. Roeleveld
2018-09-25  7:28             ` gevisz
2018-09-26 12:17               ` Bill Kenworthy

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=22618763.9V1QOtgDSA@eve \
    --to=joost@antarean.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