From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: 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: Fri, 20 Mar 2020 16:45:51 -0700 [thread overview]
Message-ID: <eb9037a20c81b189468eee3e4849f2707b49278e.camel@perches.com> (raw)
In-Reply-To: <20200320173119.2707c083@lwn.net>
On Fri, 2020-03-20 at 17:31 -0600, Jonathan Corbet wrote:
> On Sat, 14 Mar 2020 14:13:59 -0700
> Joe Perches <joe@perches.com> wrote:
>
> > fallthrough was added as a pseudo-keyword by commit 294f69e662d1
> > ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use")
> >
> > Add fallthrough as a keyword to the example .emacs content
> > so emacs can colorize or highlight the uses.
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
> > ---
> >
> > I've no idea how to remove the infinite monkeys jibe from the chinese translation
>
> Removing the "jibe" is a second change for this patch, and one which is
> not reflected in the changelog. If we want to sanitize the docs that's
> something we can talk about, but I don't want to sneak such changes in.
And I don't want to bother with the naysayers.
prev parent reply other threads:[~2020-03-20 23:47 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
2020-03-20 23:31 ` Jonathan Corbet
2020-03-20 23:45 ` Joe Perches [this message]
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=eb9037a20c81b189468eee3e4849f2707b49278e.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 \
/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).