public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke-jr@utopios.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Is anyone a prude?
Date: Tue, 1 Mar 2005 08:32:09 +0000	[thread overview]
Message-ID: <200503010832.11825.luke-jr@utopios.org> (raw)
In-Reply-To: <42240CFC.7060002@cox.net>

On Tuesday 01 March 2005 06:34, D. Wokan wrote:
> Luke-Jr wrote:
> >On Sunday 27 February 2005 22:34, Stephen P. Becker wrote:
> >>While you are at it, you should also kick any person that says WTF since
> >>*everyone* knows they just said "what the fuck" in front of the whole
> >>channel.
> >
> >I'm sure that I'm not the only person who uses "WTF" as an abbreviation
> > for "what the fsck" instead of the more common acronym.
>
> You're still only one step removed as everyone with even one geek gene
> in their DNA knows you're just slipping a geek-slanged "what the fuck"

Sure... and Ciaran *really* meant to ask about prunes, not prudes...

> using an unfortunate program name abbreviation past a censorship filter
> and everyone without thinks you just made a typo saying "what the fuck"
> or did it on purpose to get past a censorship filter.

It may not be proper English (does anyone care too much for that?), but 'what 
the fsck' actually has meaning. Something along the lines of 'what [ just 
happened | are you talking about ]? sounds like something that should be run 
through fsck.' (basically, it didn't make sense).
If the alternate 'wtf' has an actual meaning, I'm not sure I know what it is. 
When I want to get the same idea as alt-'wtf' across, I generally use 'wtc'-- 
'what the crap'-- which makes no more sense than alt-'wtf' does.
-- 
Luke-Jr
Developer, Utopios
http://utopios.org/
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-03-01  8:30 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 20:44 [gentoo-dev] Is anyone a prude? Ciaran McCreesh
2005-02-26 21:10 ` Jose Mª Calvillo aka Lechucks
2005-02-26 23:09   ` Collins Richey
2005-02-27  0:31     ` Ioannis Aslanidis
2005-02-27  9:17   ` purslow
2005-02-27  9:28     ` Daniel Armyr
2005-02-27  9:40       ` purslow
2005-02-27  9:49         ` Krzysiek Pawlik
2005-02-27 13:54           ` purslow
2005-02-27 14:13             ` Krzysiek Pawlik
2005-02-27 14:52               ` znmeb
2005-02-27 15:07                 ` Ciaran McCreesh
2005-02-27 19:30                   ` Nick Dimiduk
2005-02-28  4:17                     ` M. Edward (Ed) Borasky
2005-02-27 15:20                 ` Simon Stelling
2005-02-27 17:40                 ` Colin Kingsley
2005-02-27 18:01                   ` Ciaran McCreesh
2005-03-01  6:23                 ` D. Wokan
2005-02-27  9:54         ` Lars Strojny
2005-02-27 13:50           ` purslow
2005-02-27 14:04             ` Lars Strojny
2005-02-27 18:03               ` purslow
2005-02-27 18:17                 ` Stephen P. Becker
2005-03-01  6:28                   ` D. Wokan
2005-02-27 18:18                 ` Ciaran McCreesh
2005-02-27 20:36   ` John David Robinson
2005-02-27 20:52     ` Jon Portnoy
2005-02-27 20:56     ` Ciaran McCreesh
2005-02-27 22:51       ` John David Robinson
2005-02-27 21:45     ` Grant Goodyear
2005-02-27 21:52       ` Ciaran McCreesh
2005-02-27 21:28 ` Jason S
2005-02-27 21:36   ` Ciaran McCreesh
2005-02-27 21:42     ` Jason S
2005-02-27 21:48       ` Ciaran McCreesh
2005-02-27 21:51       ` Stephen P. Becker
2005-02-27 22:05         ` Jason S
2005-02-27 22:34           ` Stephen P. Becker
2005-02-27 22:53             ` Jason S
2005-02-27 23:14             ` Luke-Jr
2005-03-01  6:34               ` D. Wokan
2005-03-01  8:32                 ` Luke-Jr [this message]
2005-02-27 22:54           ` Kumba
2005-02-27 23:07             ` Jason S
2005-02-27 23:55               ` Kumba
2005-03-01  6:36               ` D. Wokan
2005-02-27 21:59   ` Grant Goodyear
2005-02-27 22:07     ` Stephen P. Becker
2005-02-27 22:31       ` Jason S
2005-02-27 22:39         ` Stephen P. Becker
2005-02-27 22:20     ` Jason S
2005-02-27 23:11     ` Lina Pezzella
2005-02-27 23:24       ` Jason S
2005-02-28  0:12         ` Lina Pezzella
2005-02-28  0:29           ` Jason S
2005-03-01  6:49         ` D. Wokan
2005-02-27 23:32       ` Georgi Georgiev
2005-02-28  1:40         ` Bill Davidson
2005-02-28  1:40           ` Andrew Gaffney
2005-02-28  6:07           ` W.Kenworthy
2005-03-01  6:51             ` D. Wokan
2005-03-01  7:24               ` tchiwam
2005-02-27 23:55       ` Kumba
2005-02-28 19:28       ` Jane Lee
2005-02-28 19:39         ` Nick Dimiduk
2005-02-28 23:11           ` Jane Lee
2005-03-01  6:45       ` D. Wokan
2005-02-27 22:41 ` Lance Albertson
2005-02-27 23:03   ` Ciaran McCreesh
2005-02-27 23:14     ` Jason S
2005-03-05 21:29     ` Benjamin A. Collins
2005-03-05 21:42       ` Benjamin A. Collins
2005-03-05 23:46       ` M. Edward (Ed) Borasky
2005-02-28 10:23   ` Spider
2005-02-28 14:41     ` M. Edward (Ed) Borasky
2005-02-28 16:19       ` Ciaran McCreesh
2005-03-01  7:15 ` tchiwam
2005-03-01  8:23   ` Ciaran McCreesh
2005-03-01  9:53     ` tchiwam
2005-03-02  9:54       ` Luca Barbato

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=200503010832.11825.luke-jr@utopios.org \
    --to=luke-jr@utopios.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.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