public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: jvickers@acorn.com
Cc: kenner@vlsi1.ultra.nyu.edu, davem@dm.cobaltmicro.com,
	gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: GCC2 merging (was "native language support now available")
Date: Sun, 11 Oct 1998 06:46:00 -0000	[thread overview]
Message-ID: <199810111159.HAA04640@psilocin.gnu.org> (raw)
In-Reply-To: <36124B3B.3CF9EDF5@acorn.com>

    > We also would like these companies and
    > others to get the benefits of work in EGCS that's ready for production use.

    Perhaps it's time to drop the "experimental", which was only
    ever really a polite fiction.

When Gumby told me about his intention to start another branch in GCC
development.  I objected that it was likely to result in a permanent
fork.  He made a promise to the GNU project that he would prevent
this, by designating the new branch for experimental use only.  The
word "experimental" was put in the name in order to inform the public
of this.

As a factual matter, this promise has not been kept.

You're saying that this promise was a deliberate lie from the
beginning.  I don't know if you're right, but I see you enjoy thinking
so.

Do you really have so little respect for the GNU project that you
smile at the idea of making a dishonest promise to it?


  parent reply	other threads:[~1998-10-11  6:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9809301153.AA05597@vlsi1.ultra.nyu.edu>
1998-09-30 12:52 ` John Vickers
1998-09-30 19:18   ` Alexandre Oliva
1998-10-01  3:27     ` John Vickers
1998-10-01 17:50       ` Alexandre Oliva
1998-10-01 11:53     ` Gary V. Vaughan
1998-10-11  6:46   ` Richard Stallman [this message]
1998-10-11 13:16     ` David Edelsohn
1998-10-11 15:24     ` Toon Moene
1998-10-11 15:24     ` GCC2 Gerald Gutierrez
1998-10-12 20:53     ` GCC2 merging (was "native language support now available") Joe Buck
1998-10-12 22:24       ` Richard Stallman
     [not found] <9810011131.AA10519@vlsi1.ultra.nyu.edu>
1998-10-01 12:49 ` John Vickers
1998-10-01 18:51   ` Alexandre Oliva
     [not found] ` <orn27gyple.fsf.cygnus.gcc2@araguaia.dcc.unicamp.br>
1998-10-03  0:00   ` Jason Merrill
1998-10-01 18:51 Mike Stump
1998-10-11 15:24 Richard Kenner
1998-10-11 19:05 Richard Kenner
1998-10-11 15:24 ` Jeffrey A Law
1998-10-11 19:05 ` David Edelsohn
1998-10-11 21:38 ` J. Kean Johnston
1998-10-12  5:47 Richard Kenner
1998-10-12 14:32 ` Joe Buck
1998-10-12 16:07 James Mansion
1998-10-12 22:24 ` Richard Stallman
1998-10-13 20:57   ` Alex Buell
1998-10-14 18:58     ` Joe Buck
     [not found] <None>
1998-10-13  4:54 ` Richard Kenner
1998-10-13 19:22   ` joel
1998-10-13 19:22   ` Ben Scherrey
     [not found]   ` <908312380.24418@noris.de>
1998-10-16  4:10     ` Matthias Urlichs
1998-10-16 22:01       ` Richard Earnshaw
1998-10-13 12:26 Charles M. Hannum
1998-10-13 19:22 Richard Kenner
1998-10-14  6:09 Richard Kenner
1998-10-14 11:01 Marc Espie
1998-10-14 21:17 James Mansion

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=199810111159.HAA04640@psilocin.gnu.org \
    --to=rms@gnu.org \
    --cc=davem@dm.cobaltmicro.com \
    --cc=egcs@cygnus.com \
    --cc=gcc2@cygnus.com \
    --cc=jvickers@acorn.com \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).