From: "Clayton Weaver" <cgweav@email.com>
To: linux-kernel@vger.kernel.org
Subject: Re: What's in a name?
Date: Fri, 10 Jan 2003 22:31:04 -0500 [thread overview]
Message-ID: <20030111033104.26980.qmail@email.com> (raw)
The whole thing has depended on gcc from day one,
so I see no valid objection to prominently give GNU
credit for providing a decent compiler and thus saving
Linus the work of inventing that before he started on
his kernel.
But most users simply don't care what it is called,
they only care whether it works.
I would guess that the name that gets used the most
informally is "Linux", simply because that is shorter
to type in email or Usenet messages than any of the
alternatives presented in this discussion. "Linux" is
thus the de facto standard name of the system,
regardless of who invented what parts of it and
who distributes it.
(It's kind of like a beer label. It could be any
brand in the world, but it's still just "beer" if
you're in a hurry.)
Regards,
Clayton Weaver
<mailto: cgweav@email.com>
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Meet Singles
http://corp.mail.com/lavalife
next reply other threads:[~2003-01-11 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 3:31 Clayton Weaver [this message]
2003-01-11 19:53 ` What's in a name? Mark Mielke
[not found] <0d1395823170a13DTVMAIL8@smtp.cwctv.net>
2003-01-10 18:42 ` Richard B. Johnson
2003-01-10 18:57 ` Valdis.Kletnieks
[not found] <0b9ad5923170a13DTVMAIL1@smtp.cwctv.net>
2003-01-10 18:36 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 8:57 Nvidia and its choice to read the GPL "differently" John Alvord
2003-01-09 15:18 ` What's in a name? Vlad@Vlad.geekizoid.com
2003-01-09 16:11 ` Richard B. Johnson
2003-01-09 16:51 ` venom
2003-01-09 17:48 ` Jesse Pollard
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=20030111033104.26980.qmail@email.com \
--to=cgweav@email.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;
as well as URLs for NNTP newsgroup(s).