From: Phil Sutter <phil@nwl.cc>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Willem de Bruijn <willemb@google.com>,
Daniel Axtens <dja@axtens.net>,
Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>,
Stefano Brivio <sbrivio@redhat.com>, Yonghong Song <yhs@fb.com>,
Paolo Abeni <pabeni@redhat.com>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: [PATCH RFC 15/15] net: replace **** with a hug
Date: Mon, 3 Dec 2018 11:15:06 +0100 [thread overview]
Message-ID: <20181203101506.GM30790@orbyte.nwl.cc> (raw)
In-Reply-To: <20181130192737.15053-16-jarkko.sakkinen@linux.intel.com>
On Fri, Nov 30, 2018 at 11:27:24AM -0800, Jarkko Sakkinen wrote:
> In order to comply with the CoC, replace **** with a hug.
This is incorrect: The patch doesn't replace '****', but 'fuck' instead.
> - /* Fuck, we are miserable poor guys... */
> + /* Hug, we are miserable poor guys... */
I fail to see the benefit from doing that. If I wrote: "Hug you you
hugging hug", you would still find it offensive as long as you know what
"hug" is supposed to translate into. And if you don't, you'll soon find
out.
A more constructive approach to replacing "fuck this and that" than
simply applying 's/fuck/whatever/' would be to provide details what
exactly is so bad about this and that. Of course that's not possible
without considerable effort, unlike your approach which doesn't alter
what is written but merely which words are used for it.
Cheers, Phil
next prev parent reply other threads:[~2018-12-03 10:15 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181130192737.15053-1-jarkko.sakkinen@linux.intel.com>
2018-11-30 19:27 ` [PATCH RFC 01/15] MIPS: replace **** with a hug Jarkko Sakkinen
2018-11-30 19:57 ` Jarkko Sakkinen
2018-11-30 21:06 ` Nikolay Borisov
2018-11-30 21:50 ` Jarkko Sakkinen
2018-11-30 22:11 ` Nikolay Borisov
2018-11-30 21:13 ` Al Viro
2018-11-30 21:28 ` Randy Dunlap
2018-12-01 1:52 ` Joshua Kinard
2018-12-01 4:58 ` Mike Galbraith
2018-11-30 19:27 ` [PATCH RFC 02/15] Documentation: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 03/15] drm/nouveau: " Jarkko Sakkinen
2018-11-30 20:13 ` Diego Viola
2018-11-30 21:26 ` Jarkko Sakkinen
2018-11-30 22:03 ` Diego Viola
2018-11-30 19:27 ` [PATCH RFC 04/15] m68k: " Jarkko Sakkinen
2018-11-30 19:44 ` John Paul Adrian Glaubitz
2018-11-30 20:59 ` Jarkko Sakkinen
2018-11-30 21:59 ` Jiri Kosina
2018-11-30 19:27 ` [PATCH RFC 05/15] parisc: " Jarkko Sakkinen
2018-11-30 22:48 ` Dennis Clarke
2018-11-30 23:03 ` Jarkko Sakkinen
2018-11-30 23:05 ` Diego Viola
2018-11-30 19:27 ` [PATCH RFC 06/15] cpufreq: " Jarkko Sakkinen
2018-12-03 9:08 ` Rafael J. Wysocki
2018-11-30 19:27 ` [PATCH RFC 07/15] ide: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 08/15] media: " Jarkko Sakkinen
2018-12-01 8:01 ` Tomasz Figa
2018-11-30 19:27 ` [PATCH RFC 09/15] mtd: " Jarkko Sakkinen
2018-11-30 19:39 ` Boris Brezillon
2018-11-30 20:56 ` Jarkko Sakkinen
2018-12-01 10:31 ` Richard Weinberger
2018-11-30 19:27 ` [PATCH RFC 10/15] net/sunhme: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 11/15] scsi: " Jarkko Sakkinen
2018-11-30 20:21 ` James Bottomley
2018-11-30 21:30 ` Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 12/15] inotify: " Jarkko Sakkinen
2018-12-01 6:40 ` Amir Goldstein
2018-12-05 9:49 ` Jan Kara
2018-11-30 19:27 ` [PATCH RFC 13/15] irq: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 14/15] lib: " Jarkko Sakkinen
2018-11-30 19:41 ` Steven Rostedt
2018-11-30 19:46 ` Jonathan Corbet
2018-11-30 19:49 ` Jiri Kosina
2018-11-30 20:59 ` Jarkko Sakkinen
2018-12-02 3:24 ` Sergey Senozhatsky
2018-12-02 21:34 ` Tobin C. Harding
2018-11-30 19:27 ` [PATCH RFC 15/15] net: " Jarkko Sakkinen
2018-12-03 10:15 ` Phil Sutter [this message]
2018-11-30 19:40 ` [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Kees Cook
2018-11-30 19:48 ` Fwd: " Kees Cook
2018-11-30 20:42 ` Aaro Koskinen
2018-11-30 19:56 ` Davidlohr Bueso
2018-11-30 20:12 ` Jens Axboe
2018-11-30 20:34 ` Michael Schmitz
2018-11-30 20:35 ` David Miller
[not found] ` <2007856.n5V9iKLVsV@eth7>
2018-11-30 20:42 ` David Miller
[not found] ` <2269948.6tYQeUj9R1@eth7>
2018-11-30 20:53 ` Steven Rostedt
2018-11-30 20:43 ` Steven Rostedt
2018-12-01 4:08 ` Jarkko Sakkinen
2018-11-30 21:42 ` Jarkko Sakkinen
2018-11-30 21:47 ` David Miller
2018-11-30 21:53 ` Jens Axboe
2018-11-30 20:34 ` David Miller
2018-11-30 20:55 ` Jarkko Sakkinen
2018-11-30 21:01 ` James Bottomley
2018-11-30 21:44 ` Jarkko Sakkinen
2018-11-30 21:48 ` David Miller
2018-11-30 21:54 ` Jarkko Sakkinen
2018-11-30 22:04 ` James Bottomley
2018-11-30 21:57 ` James Bottomley
2018-11-30 22:12 ` Jarkko Sakkinen
2018-11-30 22:14 ` Jonathan Corbet
2018-11-30 22:26 ` Jarkko Sakkinen
2018-11-30 22:29 ` Jarkko Sakkinen
2018-11-30 22:30 ` James Bottomley
2018-11-30 22:40 ` Jarkko Sakkinen
2018-11-30 23:28 ` Jarkko Sakkinen
2018-12-01 8:20 ` Geert Uytterhoeven
2018-12-07 13:39 ` Eric Curtin
2018-11-30 22:26 ` James Bottomley
2018-11-30 21:02 ` Steven Rostedt
2018-11-30 21:04 ` Jonathan Corbet
2018-11-30 19:57 ` Geert Uytterhoeven
2018-11-30 21:09 ` Jarkko Sakkinen
2018-11-30 20:09 ` John Paul Adrian Glaubitz
2018-11-30 21:32 ` Jarkko Sakkinen
2018-11-30 20:31 ` Matthias Brugger
2018-11-30 21:34 ` Jarkko Sakkinen
2018-11-30 21:07 ` Jarkko Sakkinen
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=20181203101506.GM30790@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=davem@davemloft.net \
--cc=dja@axtens.net \
--cc=edumazet@google.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbrivio@redhat.com \
--cc=willemb@google.com \
--cc=yhs@fb.com \
/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).