From: "J. Dow" <jdow@earthlink.net>
To: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@ivimey.org>,
"Andrew Morton" <akpm@zip.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19pre7aa1
Date: Sat, 20 Apr 2002 15:56:58 -0700 [thread overview]
Message-ID: <0d6901c1e8be$acfe6cf0$1125a8c0@wednesday> (raw)
In-Reply-To: <Pine.LNX.4.33.0204202310360.21635-100000@sharra.ivimey.org>
From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@ivimey.org>
> On Sat, 20 Apr 2002, Andrew Morton wrote:
>
> >[1] Can we please not that term? A "flush" is something which you
> > do to a "dunny" after taking a "crap". [2]
> >
> > Caches are either "written back" or are "invalidated". Nothing
> > else.
>
> I would agree with this: until a couple of years ago, I wasn't even aware that
> there were two options here: now I know, but I'm sure others don't.
>
> >[2] And a "sync" is something which you wash your hands in after the
> > "flush".
>
> Well, actually the thing you wash in is a "sink". The term "sync" comes from
> synchronise (or -ize in American).
And I presume anyday now some twit will attempt to get the "fork" the
fork out of there, too. (I actually experienced this attempt once on a
DoD project I supported. The incompetent source code reviewers in DC
objected to "fork" as profanity thinly cloaked. It took a several page
letter citing the term's use in the art and related literature to get
the anal retentive creep to back down.)
"Flush" is a well known term of art. And as you note, Ruth, "sync" is
short for synchronize. Is cleaning up the use of language in the computer
arts the purpose we are all here?
{O.O} A rather bemused and astonished Joanne Dow.
next prev parent reply other threads:[~2002-04-20 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 17:42 2.4.19pre7aa1 Andrea Arcangeli
2002-04-20 19:37 ` 2.4.19pre7aa1 Andrew Morton
2002-04-20 21:38 ` 2.4.19pre7aa1 Andrea Arcangeli
2002-04-20 22:12 ` 2.4.19pre7aa1 Ruth Ivimey-Cook
2002-04-20 22:56 ` J. Dow [this message]
2002-04-21 0:09 ` 2.4.19pre7aa1 Anton Blanchard
2002-04-20 23:57 ` 2.4.19pre7aa1 Anton Blanchard
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='0d6901c1e8be$acfe6cf0$1125a8c0@wednesday' \
--to=jdow@earthlink.net \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=akpm@zip.com.au \
--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