From: David Masterson <dmaster@synopsys.com>
Subject: Re: A rose by any other name (was Re: [OT] Re: configure script)
Date: 13 Jun 2002 16:23:22 -0700 [thread overview]
Message-ID: <ufzzqvk45.fsf@synopsys.com> (raw)
In-Reply-To: vohvg8mvnwp.fsf@math.berkeley.edu
[followups to gnu.misc.discuss]
>>>>> David desJardins writes:
> Richard Stallman <rms@gnu.org> writes:
>> Calling the system GNU/Linux is easiest and most efficient way to
>> help correct the confusion.
> My experience is that this doesn't work for anyone. The people who
> understand the history and the components already have an opinion.
> The people who don't know the history or the components think, at
> most, that GNU/Linux is some sort of variant of Linux, like
> "FreeBSD" is a spinoff of BSD, and "SCO Unix" was a spinoff of Unix.
Or "RedHat Linux" and "SuSE Linux"...
> On the other hand, I don't have any problem with the request, and I
> don't understand why Mr Kastrup rants about it.
From what I've seen, my guess would be that he feels (rightly or
wrongly) that it is a request that comes from RMS and not really from
"all the contributors to GNU". Since the GNU project is such an open
and eclectic project that has been going on for 18 years and
comprising hundreds or thousands of people, it's hard to ascribe a lot
of weight to the request of one member of the project (even when it is
RMS). Some (like Mr. Kastrup) might think that the copyright all over
the code would be enough. Had the request come sooner in the life of
"Linux" (say, around the time it started to graduate from kernel to
O/S), then acceptance of the GNU moniker might've been easier (there
is also the notorious tendency of software engineers to shorten names
to combat).
--
David Masterson David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer Synopsys, Inc.
Software Engineering Sunnyvale, CA
next prev parent reply other threads:[~2002-06-13 23:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 18:44 configure script Edson Alves Pereira
2002-06-08 19:15 ` Richard Stallman
2002-06-12 10:23 ` Sami Sihvonen
2002-06-12 10:40 ` David Kastrup
2002-06-12 17:42 ` Paul Jarc
2002-06-12 18:53 ` [OT] " Glenn Morris
2002-06-12 19:34 ` A rose by any other name (was Re: [OT] Re: configure script) David Masterson
2002-06-13 21:46 ` Richard Stallman
2002-06-13 22:01 ` David desJardins
2002-06-13 23:23 ` David Masterson [this message]
2002-06-15 14:13 ` Richard Stallman
2002-06-13 23:48 ` David Kastrup
2002-06-18 10:08 ` Sami Sihvonen
2002-06-12 20:24 ` [OT] Re: configure script Peter S Galbraith
2002-06-12 21:32 ` David Kastrup
2002-06-12 22:24 ` David Masterson
2002-06-13 5:39 ` Eli Zaretskii
2002-06-13 8:52 ` David Kastrup
2002-06-13 11:34 ` Eli Zaretskii
2002-06-13 12:35 ` David Kastrup
2002-06-13 14:17 ` Eli Zaretskii
2002-06-13 14:56 ` David Kastrup
2002-06-13 15:30 ` Eli Zaretskii
2002-06-13 16:00 ` Andreas Schwab
2002-06-14 15:47 ` Richard Stallman
2002-06-12 21:03 ` Alfred M. Szmidt
2002-06-12 22:30 ` David Kastrup
2002-06-12 22:59 ` Alfred M. Szmidt
2002-06-13 8:29 ` David Kastrup
2002-06-13 19:42 ` Alfred M. Szmidt
2002-06-12 23:47 ` Richard Stallman
2002-06-13 9:01 ` David Kastrup
2002-06-17 14:57 ` Sami Sihvonen
2002-06-18 16:06 ` D. Goel
2002-06-18 18:24 ` Christoph Conrad
2002-06-12 11:00 ` Eli Zaretskii
2002-06-17 14:56 ` Sami Sihvonen
2002-06-17 16:21 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ufzzqvk45.fsf@synopsys.com \
--to=dmaster@synopsys.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).