[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUkpLWm5NZmYj=uMgVncw6ZOb7j9KxFoDGhrnr7vzpx_w@mail.gmail.com>
Date: Sat, 1 Dec 2018 09:20:03 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Jonathan Corbet <corbet@....net>
Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Davidlohr Bueso <dave@...olabs.net>,
Kees Cook <keescook@...omium.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
amir73il@...il.com, Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Daniel Axtens <dja@...ens.net>,
"David S. Miller" <davem@...emloft.net>,
Dominik Brodowski <linux@...inikbrodowski.net>,
DRI Development <dri-devel@...ts.freedesktop.org>,
Eric Dumazet <edumazet@...gle.com>, federico.vaga@...a.pv.it,
Geert Uytterhoeven <geert+renesas@...der.be>,
Helge Deller <deller@....de>, Joshua Kinard <kumba@...too.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
linux-ide@...r.kernel.org,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Linux MIPS Mailing List <linux-mips@...ux-mips.org>,
MTD Maling List <linux-mtd@...ts.infradead.org>,
Parisc List <linux-parisc@...r.kernel.org>,
Linux PM list <linux-pm@...r.kernel.org>,
scsi <linux-scsi@...r.kernel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
netdev <netdev@...r.kernel.org>, nouveau@...ts.freedesktop.org,
pabeni@...hat.com, Paul Burton <paul.burton@...s.com>,
Petr Mladek <pmladek@...e.com>, Rob Herring <robh@...nel.org>,
sean.wang@...iatek.com,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
shannon.nelson@...cle.com, Stefano Brivio <sbrivio@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
"Tobin C. Harding" <me@...in.cc>, makita.toshiaki@....ntt.co.jp,
Willem de Bruijn <willemb@...gle.com>, yhs@...com,
yanjun.zhu@...cle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3
Hi Jon,
On Fri, Nov 30, 2018 at 11:15 PM Jonathan Corbet <corbet@....net> wrote:
> On Fri, 30 Nov 2018 14:12:19 -0800
> Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com> wrote:
>
> > As a maintainer myself (and based on somewhat disturbed feedback from
> > other maintainers) I can only make the conclusion that nobody knows what
> > the responsibility part here means.
> >
> > I would interpret, if I read it like at lawyer at least, that even for
> > existing code you would need to do the changes postmorterm.
> >
> > Is this wrong interpretation? Should I conclude that I made a mistake
> > by reading the CoC and trying to understand what it *actually* says?
> > After this discussion, I can say that I understand it less than before.
>
> Have you read Documentation/process/code-of-conduct-interpretation.rst?
> As has been pointed out, it contains a clear answer to how things should
> be interpreted here.
Indeed:
| Contributions submitted for the kernel should use appropriate language.
| Content that already exists predating the Code of Conduct will not be
| addressed now as a violation.
However:
| Inappropriate language can be seen as a
| bug, though; such bugs will be fixed more quickly if any interested
| parties submit patches to that effect.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists