From: Jiri Kosina <jikos@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus?
Date: Sun, 9 Sep 2018 22:05:59 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1809092200470.15880@cbobk.fhfr.pm> (raw)
In-Reply-To: <20180908074708.249571f4@coco.lan>
On Sat, 8 Sep 2018, Mauro Carvalho Chehab wrote:
> Q: How many Kernel developers does it take to replace Linus?
Somebody please remind me, what problem exactly are we trying to solve
here, again? :)
I honestly believe this all started as a joke from James (the mixed up
conferences etc. of course providing excellent grounds for such a joke :)
), but now that this keeps going on, I think the problem that is actually
being solved (and what would be the properties of expected
outcome/solution) should be formulated again :)
Linus explicitly stated that he's willing to go on merging, and we don't
have any "bus factor" plans for other critical people either anyway.
So if this "how do we generally deal with all the buses out there?", so be
it, but it really should be clearly stated I think :)
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-09-09 20:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:44 [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus? James Bottomley
2018-09-06 19:47 ` Daniel Vetter
2018-09-06 19:51 ` James Bottomley
2018-09-06 20:06 ` Geert Uytterhoeven
2018-09-06 20:35 ` Olof Johansson
2018-09-06 20:45 ` Linus Torvalds
2018-09-06 20:52 ` Olof Johansson
2018-09-08 10:47 ` Mauro Carvalho Chehab
2018-09-08 10:50 ` Thomas Gleixner
2018-09-08 12:21 ` Daniel Vetter
2018-09-09 13:56 ` Laurent Pinchart
2018-09-09 20:05 ` Jiri Kosina [this message]
2018-09-06 19:57 ` Linus Torvalds
2018-09-06 20:51 ` James Bottomley
2018-09-06 20:59 ` Linus Torvalds
2018-09-06 21:13 ` James Bottomley
2018-09-06 21:20 ` Jens Axboe
2018-09-06 21:28 ` John W. Linville
2018-09-06 21:34 ` Jens Axboe
2018-09-06 21:41 ` Linus Torvalds
2018-09-06 22:12 ` David Woodhouse
2018-09-06 22:19 ` Linus Torvalds
2018-09-06 22:29 ` James Bottomley
2018-09-06 21:37 ` Olof Johansson
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=nycvar.YFH.7.76.1809092200470.15880@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab+samsung@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).