From: Matt Mackall <mpm@selenic.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: gene.heskett@verizon.net, linux-kernel@vger.kernel.org,
robustmutexes@lists.osdl.org
Subject: Re: [RFC/PATCH] FUSYN 5/10: kernel fuqueues
Date: Thu, 11 Dec 2003 21:23:01 -0600 [thread overview]
Message-ID: <20031212032301.GF23787@waste.org> (raw)
In-Reply-To: <A20D5638D741DD4DBAAB80A95012C0AE0125E23B@orsmsx409.jf.intel.com>
On Thu, Dec 11, 2003 at 07:15:40PM -0800, Perez-Gonzalez, Inaky wrote:
> > From: Matt Mackall [mailto:mpm@selenic.com]
>
>
> > > > From: Gene Heskett [mailto:gene.heskett@verizon.net]
> > > >
> > > > inaky.perez-gonzalez@intel.com wrote:
> > > > >> include/linux/fuqueue.h | 451
> > > > >> ++++++++++++++++++++++++++++++++++++++++++++++++
> > > > >> include/linux/plist.h | 197 ++++++++++++++++++++
> > > > >> kernel/fuqueue.c | 220 +++++++++++++++++++++++
> > > > >> 3 files changed, 868 insertions(+)
> > > > >>
> > > > >> +++ linux/include/linux/fuqueue.h Wed Nov 19 16:42:50 2003
> > > > >
> > > > >I don't suppose you've run this feature name past anyone in
> > > > > marketting or PR?
> > > >
> > > > Obviously not...
> > >
> > > I am already asking for new names for whoever doesn't like
> > > them, like me ... I have more interesting things to do than
> > > looking for names.
> >
> > The name's fine by me actually, I'm greatly looking forward to hearing
> > someone present them at the next Linux Symposium.
>
> I'll try to [at least I'll submit a proposal]...heh! :]
>
> > Other people might not be so amused, though.
>
> Do you mean on how similar it sounds to the famous four letter
> word that everybody seems to be afraid to say in public? :)
>
> Well, I had initially (and intentionally) fucvar for a conditional
> variable...however, in order to be more in order with how POSIX names
> them, I changed it to fucond.
>
> Good thing they were not worth to implement (and actually swearing
> by them was a good thing, they were a real PITA).
>
> Now seriously, forgive my naivete as English is my second language,
> what might be not so amusing to others? the 'fuck' thingie?
The obvious pronunciation is closer to "fuck you" (fuh-queue or
fuq-ueue), which is a little more pointed.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next prev parent reply other threads:[~2003-12-12 3:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 3:15 [RFC/PATCH] FUSYN 5/10: kernel fuqueues Perez-Gonzalez, Inaky
2003-12-12 3:23 ` Matt Mackall [this message]
2003-12-12 22:43 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 22:50 [RFC/PATCH] FUSYN 4/10: Support for ia64 inaky.perez-gonzalez
2004-01-14 22:50 ` [RFC/PATCH] FUSYN 5/10: kernel fuqueues inaky.perez-gonzalez
2003-12-13 1:05 Perez-Gonzalez, Inaky
2003-12-12 23:02 watermodem
2003-12-13 6:09 ` Valdis.Kletnieks
2003-12-12 3:26 Perez-Gonzalez, Inaky
2003-12-12 0:06 Perez-Gonzalez, Inaky
2003-12-12 2:57 ` Matt Mackall
[not found] <0312030051..akdxcwbwbHdYdmdSaFbbcycyc3a~bzd25502@intel.com>
2003-12-03 8:51 ` inaky.perez-gonzalez
2003-12-11 23:30 ` Matt Mackall
2003-12-11 23:55 ` Gene Heskett
2003-12-14 16:15 ` Pavel Machek
2003-12-12 19:21 ` William Lee Irwin III
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=20031212032301.GF23787@waste.org \
--to=mpm@selenic.com \
--cc=gene.heskett@verizon.net \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robustmutexes@lists.osdl.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