LKML Archive on
 help / Atom feed
From: Luke Kenneth Casson Leighton <>
To: Linus Torvalds <>,
	Linux Kernel Mailing List <>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Sun, 30 Sep 2018 12:47:12 +0100
Message-ID: <> (raw)
In-Reply-To: <>

linus: ah... um... okay so this is beginning to remind me of dr who
films, the comedy film "the world's end", and various other b-movie
horror shows where people were taken over through mind-control or

so i apologise, i'm going to stop pussy-footing around and ask HAVE

*cough*.  enough NLP-esque shock tactics with a bit of comedy thrown
in to take the sting out of it... allow me to return to rational

(1) you apologised for your behaviour, and it's fantastic that you
recognised that there was a problem and asked for help.  however, you
*may* be feeling a little guilty, and it's clearly knocked your
confidence, and that unfortunately has allowed political correctness
to "creep in" where we know it never, ever belongs: in engineering.

the next thing you know, the fucking guilt-ridden morons who want the
words "master" and "slave" erased from the history books will be
telling you that we have to change SPI's "MOSI" and "MISO" to...
god... i dunno... "ROWI and RIWO" - "requestor" and "worker" or
something incredibly stupid:

Requestor: "i'm awfully sorry, if you wouldn't mind, if it's not too
much trouble mr worker, when you have the time and you're not on your
union-mandated break, could you deal with this bit-change for me?"

(2) more and more people are raising the fact that the change was made
without consultation.  this *is* going to bite everyone.  i strongly,
strongly suggest reverting it: i made the point very clear that it
wasn't the actual CoC that was the problem, it was that you, yourself,
were not really obeying it (so nobody else could, either).

(3) let's look at what toxic documents named "codes of conduct" look
like from an engineering perspective:

                                            BEHAVIOUR_NAZI |
                                            BEHAVIOUR_RELIGIOUS_EXTREMIST ....
                                            BEHAVIOUR_ANTI_CHRISTIAN \
                                            BEHAVIOUR_ANTI_MUSLIM \
// oops fuck we're gonna run out of bits extremely quickly....

do you see where that's going?  do you get the point already?  if an
engineer proposed the above patch to create the toxic CoC document
that insidiously crept in recently, you and pretty much everyone would
think that the submitter had a fucking screw loose and needed
psychiatric help.

these toxic documents do not have to spell it out, but they *imply*
that there are (deep breath...) spics, wocs, niggers, honky white
bastards, chinks kooks and their mothers too all trying to ATTACK the
project, and we'd better make sure that they're all excluded,
otherwise we're all in trouble, eh?

i apologise for using these words: if you are a decent human being you
should by now feeling physically sick to your stomach at having read
that paragraph, that those words were even used... yet they're not
actually *in* that toxic document, but they don't have to be: people
are still thinking them.  like the "don't think of a pink elephant"
our subconscious mind cannot help by strip out the "don't".

bottom line: the *entire linux kernel project* has now been
*completely poisoned* by that document.

put another way: an engineer would go, "wtf??" and would say "we don't
need to fill every single bit in the bitfield and then invert it for
god's sake!  just say "good behaviour is expected" and be done with

so why not say, instead of that absolute god-awful list, "everyone is
welcome; everyone belongs".  you see the difference?  you see how
simple and empowering that is?  it's INVITING people to participate,
and it's pretty obvious that if someone feels *UN*welcome, the rules
have been broken and they can raise it as an issue.  rather than
absolutely terrifying and sickening absolutely everybody.

the analogy is the story of mother theresa being invited to an
"anti-war" rally.  she declined... and said, "if ever you hold a PEACE
rally, i'd be delighted to attend".

so come on, linus: wake up, man.  just because this is outside of your
area of expertise does not mean that you have to let go of the reins.
*get a grip*.  use your engineering expertise, apply it to the
problem, work with *EVERYONE* and work out an *ACCEPTABLE* solution.



  parent reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17  2:15 Luke Kenneth Casson Leighton
2018-09-18  2:10 ` Luke Kenneth Casson Leighton
2018-09-30 11:47 ` Luke Kenneth Casson Leighton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-17  8:53 […] " Martin Steigerwald
2018-09-30 12:09 ` Re: Linux 4.19-rc4 released, " lkcl
2018-09-30 14:07   ` Martin Steigerwald
2018-09-30 16:27     ` Luke Kenneth Casson Leighton
2018-09-16 19:22 Linus Torvalds
2018-09-17  0:18 ` Rene Herman
2018-09-17  0:23 ` Rene Herman
2018-09-17  6:57 ` opal hart
2018-09-17 12:58 ` Guenter Roeck
2018-09-17 17:09 ` Joe Perches
2018-09-17 21:09 ` Michael Woods
2018-09-18  1:30   ` Pavel Snajdr
2018-09-21 22:13     ` Michael Woods
2018-10-04 14:57     ` ebiederm
2018-10-08 15:29       ` Enrico Weigelt, metux IT consult
2018-10-08 13:54     ` Enrico Weigelt, metux IT consult
2018-10-08 16:36 ` Enrico Weigelt, metux IT consult

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox