From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
swboyd@chromium.org, tiwai@suse.de, nfraprado@protonmail.com,
mchehab+huawei@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org, Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: Re: [PATCH] docs: kernel-hacking: Remove the word fuck,trying to be civil :)
Date: Thu, 11 Feb 2021 10:04:07 -0700 [thread overview]
Message-ID: <87sg62pmd4.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210205115951.1276526-1-unixbhaskar@gmail.com>
Bhaskar Chowdhury <unixbhaskar@gmail.com> writes:
> s/fuck//
>
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Documentation/kernel-hacking/locking.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
> index c3448929a824..ed1284c6f078 100644
> --- a/Documentation/kernel-hacking/locking.rst
> +++ b/Documentation/kernel-hacking/locking.rst
> @@ -958,7 +958,7 @@ grabs a read lock, searches a list, fails to find what it wants, drops
> the read lock, grabs a write lock and inserts the object has a race
> condition.
>
> -If you don't see why, please stay the fuck away from my code.
> +If you don't see why, please stay away from my code.
Sigh.
I've gotten a few variants of this patch over the years...I guess maybe
the time has come to apply one, so I did. If the word is too offensive
to be in our docs, though, perhaps it shouldn't be in the changelog
either, so I rewrote it:
docs: kernel-hacking: be more civil
Remove the f-bomb from locking.rst. Let's have a moment of silence,
though, as we mark the passing of the last of Rusty's once plentiful
profanities in this venerable document.
Thanks,
jon
next prev parent reply other threads:[~2021-02-11 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 11:59 [PATCH] docs: kernel-hacking: Remove the word fuck,trying to be civil :) Bhaskar Chowdhury
2021-02-11 17:04 ` Jonathan Corbet [this message]
2021-02-11 17:10 ` Randy Dunlap
2021-02-12 8:23 ` Bhaskar Chowdhury
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=87sg62pmd4.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.com \
--cc=rdunlap@infradead.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.de \
--cc=unixbhaskar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.