linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Harry Wei <harryxiyou@gmail.com>,
	Alex Shi <alex.shi@linux.alibaba.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coding-style.rst: Add fallthrough as an emacs keyword
Date: Sat, 14 Mar 2020 21:26:13 -0700	[thread overview]
Message-ID: <e8c0df0e7adb53c2e16f5a4f85de9f5a0f627b4f.camel@perches.com> (raw)
In-Reply-To: <20200315021222.GU22433@bombadil.infradead.org>

On Sat, 2020-03-14 at 19:12 -0700, Matthew Wilcox wrote:
> On Sat, Mar 14, 2020 at 02:13:59PM -0700, Joe Perches wrote:
> > I've no idea how to remove the infinite monkeys jibe from the chinese translation
> 
> I don't think you should.  That's part of Linus' original text, and I
> don't think it deters contributors.
> 
> > -uses are less than desirable (in fact, they are worse than random
> > -typing - an infinite number of monkeys typing into GNU emacs would never
> > -make a good program).
> > +uses are less than desirable.

It's silly, and moderately offensive,
unrepresentative of the softer, modern Linus.



  reply	other threads:[~2020-03-15  4:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 21:13 [PATCH] coding-style.rst: Add fallthrough as an emacs keyword Joe Perches
2020-03-15  2:12 ` Matthew Wilcox
2020-03-15  4:26   ` Joe Perches [this message]
2020-03-20 23:31 ` Jonathan Corbet
2020-03-20 23:45   ` Joe Perches

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=e8c0df0e7adb53c2e16f5a4f85de9f5a0f627b4f.camel@perches.com \
    --to=joe@perches.com \
    --cc=alex.shi@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.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 NNTP newsgroup(s).