From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: driverfs question
Date: 12 Mar 2002 13:17:17 -0800 [thread overview]
Message-ID: <a6lr8t$m4t$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020221161906.254A-100000@chaos.analogic.com> <3C756D06.7090901@netscape.net>
Followup to: <3C756D06.7090901@netscape.net>
By author: Adam <ambx1@netscape.net>
In newsgroup: linux.dev.kernel
>
> You're absolutely right. What I meant to say is a directory. It's
> simply a bad habit. In fact, one, of several, reason I became
> interested in the Linux kernel project is that I was unhappy with the
> Micro$oft licensing policy. The term folder is used by micro$oft simply
> to make it's OS sound more user friendly.
>
... because, of course, that was the term Apple used.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-03-12 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 20:37 driverfs question Adam
2002-02-21 20:48 ` Patrick Mochel
2002-02-21 21:25 ` Richard B. Johnson
2002-02-21 21:56 ` Adam
2002-02-21 21:59 ` Richard B. Johnson
2002-03-12 21:17 ` H. Peter Anvin [this message]
2002-02-21 21:53 ` Greg KH
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='a6lr8t$m4t$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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