From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: binutils@sources.redhat.com, crossgcc@sources.redhat.com,
gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: An article about the Cygnus tree
Date: Mon, 04 Sep 2000 17:32:00 -0000 [thread overview]
Message-ID: <0009050030.AA26952@ivan.Harhan.ORG> (raw)
Geoff Keating <geoffk@cygnus.com> wrote:
> This bit is not correct. EGCS was never 'run by' Cygnus. It has
> always been run by a steering committee on which Cygnus has been
> careful to ensure that its employees were never a majority.
OK, I checked this in:
------- cygnus-tree-intro -------
*** /tmp/d26930 Mon Sep 4 19:22:03 2000
--- cygnus-tree-intro Mon Sep 4 19:21:02 2000
***************
*** 45,52 ****
development and do it behind closed doors. First they synchronised their work
on it (in their internal Cygnus tree) with the FSF maintainers. Then in late
1997 they created an open development project for it which they named EGCS. It
! was run by Cygnus and competed with FSF's gcc project. Finally, in spring 1999
! FSF closed their gcc project and EGCS was renamed into GCC.
All these programs have been integrated into the Cygnus tree so completely that
they no longer exist separately from it. Moreover, some of these programs are
--- 45,52 ----
development and do it behind closed doors. First they synchronised their work
on it (in their internal Cygnus tree) with the FSF maintainers. Then in late
1997 they created an open development project for it which they named EGCS. It
! was a public project and competed with FSF's gcc project. Finally, in spring
! 1999 FSF closed their gcc project and EGCS was renamed into GCC.
All these programs have been integrated into the Cygnus tree so completely that
they no longer exist separately from it. Moreover, some of these programs are
BTW, what did EGCS stand for?
> Well, I for one would like to see a combined tree.
That's why I wrote:
: Some of the GCC maintainers have said that they liked the idea. However,
: there seems to be some politics playing against it, apparently coming from
: FSF. Thus it appears that the next battle is going to be between us,
: developers, and the politicians.
--
Michael Sokolov Harhan Engineering Laboratory
Public Service Agent International Free Computing Task Force
International Engineering and Science Task Force
615 N GOOD LATIMER EXPY STE #4
DALLAS TX 75204-5852 USA
Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)
next reply other threads:[~2000-09-04 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 17:32 Michael Sokolov [this message]
2000-09-04 18:03 ` David Edelsohn
2000-09-04 18:13 ` Jan Dvorak
2000-09-04 21:06 ` Alexandre Oliva
2000-09-04 21:24 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
2000-09-06 17:49 Mike Stump
2000-09-06 17:54 ` Jeffrey A Law
2000-09-06 20:20 ` Alexandre Oliva
2000-09-06 12:45 Michael Sokolov
2000-09-06 13:05 ` David Edelsohn
2000-09-05 10:54 Michael Sokolov
2000-09-05 16:13 ` Russ.Shaw
2000-09-05 10:44 Michael Sokolov
2000-09-05 12:01 ` Joe Buck
2000-09-04 21:19 Michael Sokolov
2000-09-04 21:40 ` Russ.Shaw
2000-09-04 18:15 Michael Sokolov
2000-09-04 19:19 ` David Edelsohn
2000-09-04 14:21 Michael Sokolov
2000-09-04 16:54 ` Geoff Keating
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=0009050030.AA26952@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=binutils@sources.redhat.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.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.
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).