Date:   Fri, 7 Dec 2018 13:39:54 +0000
From:   Eric Curtin <ericcurtin17@...il.com>
To:     geert@...ux-m68k.org
Cc:     corbet@....net, jarkko.sakkinen@...ux.intel.com,
        James.Bottomley@...senpartnership.com, dave@...olabs.net,
        keescook@...omium.org,
        Kernel development list <linux-kernel@...r.kernel.org>,
        amir73il@...il.com, akpm@...ux-foundation.org,
        andriy.shevchenko@...ux.intel.com, dja@...ens.net,
        davem@...emloft.net, linux@...inikbrodowski.net,
        dri-devel@...ts.freedesktop.org, edumazet@...gle.com,
        federico.vaga@...a.pv.it, geert+renesas@...der.be, deller@....de,
        kumba@...too.org, linux-doc@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, linux-ide@...r.kernel.org,
        linux-m68k@...ts.linux-m68k.org, linux-media@...r.kernel.org,
        linux-mips@...ux-mips.org, linux-mtd@...ts.infradead.org,
        linux-parisc@...r.kernel.org, linux-pm@...r.kernel.org,
        linux-scsi@...r.kernel.org, matthias.bgg@...il.com,
        netdev@...r.kernel.org, nouveau@...ts.freedesktop.org,
        pabeni@...hat.com, paul.burton@...s.com, pmladek@...e.com,
        robh@...nel.org, sean.wang@...iatek.com,
        sergey.senozhatsky@...il.com, shannon.nelson@...cle.com,
        sbrivio@...hat.com, rostedt@...dmis.org, me@...in.cc,
        makita.toshiaki@....ntt.co.jp, willemb@...gle.com, yhs@...com,
        yanjun.zhu@...cle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3

Hi Guys,

I initially thought these patches were a joke. But I guess they are
not. I suppose 2018 is the year everything became offensive.

Could we avoid the s/fuck/hug/g though? I have nothing against
re-wording this stuff to remove the curse word, but it should at least
make sense.

What's going to happen is someone is a newbie is going to see a comment
like "We found an mark in the idr at the right wd, but it's not the
mark we were told to remove. eparis seriously hugged up somewhere",
probably google the term as they are unfamiliar with it, find out it's
an alias for "fucked" and if they are sensitive get offended anyway.

On Sat, 1 Dec 2018 at 08:20, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> 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