public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <lkml@tlinx.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Profanity in the kernel-sources
Date: Fri, 11 Jun 2004 01:45:11 -0700	[thread overview]
Message-ID: <40C97117.7040704@tlinx.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0406101638130.18878-100000@www.fnordora.org>

you could put a filter on bk and have it reject any patch applied
that has any number of a list of "naughty" words...like when I
used the word "unscrew" to describe the action to remove a screw.
I was told I couldn't post it because of the profanity (oi vey!)
Just think of the inanities...
-l

>I just find it a pointless diversion one way or another.  profanity is 
>quite descriptive when it comes to code.  (Especially device drivers.)
>
>  
>

  reply	other threads:[~2004-06-11  8:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10 18:53 Insults in the kernel-sources Tobias Hirning
2004-06-10 19:02 ` Måns Rullgård
2004-06-10 19:16   ` areversat
2004-06-10 19:11 ` Leon Woestenberg
2004-06-10 19:23 ` Richard B. Johnson
2004-06-10 20:19   ` alan
2004-06-10 21:26     ` Richard B. Johnson
2004-06-10 23:17     ` walt
2004-06-10 22:44       ` alan
2004-06-11  0:36         ` Richard B. Johnson
2004-06-10 23:52       ` Vadim Lobanov
2004-06-10 23:58         ` Tim Hockin
2004-06-11  0:34           ` James Buchanan
2004-06-10 23:47             ` alan
2004-06-11  0:38             ` Vadim Lobanov
2004-06-11  0:07     ` Nigel Cunningham
2004-06-10 23:41       ` alan
2004-06-11  8:45         ` L A Walsh [this message]
2004-06-11  7:02       ` Måns Rullgård
2004-06-14 13:46   ` Tobias Hirning
2004-06-14 19:39     ` Patrick Finnegan
2004-06-10 19:23 ` viro
2004-06-10 20:04 ` Paul P Komkoff Jr
2004-06-11 15:43 ` Jesper Juhl
2004-06-12  2:48 ` Rik van Riel
2004-06-12  6:37   ` John Bradford
2004-06-12 12:47     ` Richard B. Johnson

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=40C97117.7040704@tlinx.org \
    --to=lkml@tlinx.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