From: NeilBrown <neilb@suse.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Frank Rowand <frowand.list@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] TAB non-nomination
Date: Mon, 12 Nov 2018 15:54:56 +1100 [thread overview]
Message-ID: <87lg5yvqsf.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20181111055728.GC12818@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Sun, Nov 11 2018, Theodore Y. Ts'o wrote:
>
> At this point, Linus has indicated that he would prefer that we not
> try to tweak the CoC any further, and let's see how it works out in
> practice.
I do love this. Linus, who is apparently the cause of the problem, is
seen to be wise enough to be able to decide when we should start the
conversation, and when we should stop it.
To me, this just seems like Linus throwing his weight around in an area
where he has already demonstrated his incompetence.
Of course we cannot really see how the CoC "works out in practice"
because you changed two variables at once. Linus decided to behave
differently and a CoC was "adopted". We will never know which change
had which effect.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-11-12 4:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 0:04 [Ksummit-discuss] " James Bottomley
2018-11-09 0:29 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2018-11-09 3:30 ` [Ksummit-discuss] " Chris Mason
2018-11-09 17:52 ` Shuah Khan
2018-11-09 19:03 ` Theodore Y. Ts'o
2018-11-09 19:23 ` Joe Perches
2018-11-10 21:21 ` Theodore Y. Ts'o
2018-11-10 21:47 ` Joe Perches
2018-11-12 17:15 ` James Morris
2018-11-09 20:17 ` [Ksummit-discuss] better hot-topic discussion processes was: " Jason Cooper
2018-11-10 19:26 ` Chris Mason
2018-11-10 21:55 ` Jason Cooper
2018-11-14 18:25 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-09 19:54 ` [Ksummit-discuss] [Tech-board-discuss] " Frank Rowand
2018-11-10 19:15 ` Chris Mason
2018-11-10 21:59 ` Jason Cooper
2018-11-11 3:18 ` Frank Rowand
2018-11-11 5:57 ` Theodore Y. Ts'o
2018-11-12 4:44 ` NeilBrown
2018-11-12 4:54 ` NeilBrown [this message]
2018-11-12 17:00 ` Steven Rostedt
2018-11-13 16:49 ` Jani Nikula
2018-11-13 19:59 ` Laurent Pinchart
2018-11-14 17:28 ` Mark Brown
2018-11-09 17:19 ` [Ksummit-discuss] " Stephen Hemminger
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=87lg5yvqsf.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=frowand.list@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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