From: dewar@gnat.com
Subject: Re: SGI GNAT Question? (Long)
Date: 1999/03/10
Date: 1999-03-10T00:00:00+00:00 [thread overview]
Message-ID: <7c6te3$j81$1@nnrp1.dejanews.com> (raw)
In-Reply-To: 87lnh52i3d.fsf@mihalis.ix.netcom.com
In article <87lnh52i3d.fsf@mihalis.ix.netcom.com>,
Chris Morgan <mihalis@ix.netcom.com> wrote:
> [1]Prof. Dewar was insistent that this is true and often
> not recognized publically. I guess it's the "major
> developments" bit that is key here - perhaps the open
> informal teams are getting left behind by heretofore
> private work I don't know about, it's entirely possible.
Well you certainly can't know about the internal Cygnus
work if you have not signed a non-disclosure, and even then
they often hold their road maps quite closely even with
respect to their major customers.
The important thing to realize is that EGCS is NOT a Cygnus
project. It is independent at this stage. Yes, Cygnus has
a lot of influence, and several people on the EGCS board
are from Cygnus, and Cygnus also invests substantial
resources in keeping EGCS synchronized to some extent with
their internal tree.
But major development work that goes on in the internal
tree is not reflected day to day in the EGCS tree, and
indeed you would not want it to be in my opinion, and the
Cygnus operating procedure seems quite reasonable.
Same thing with GDB, the GDB 5.0 tree that is internal to
Cygnus is most certainly not externally visible, and
details of this tree are released only to their closest
large customers. Again, this seems entirely reasonable
to me!
As for Redhat and Linux, the same kind of relationship
exists between the internal Redhat development and the
externally visible version of Linux. In that case we know
a little more about what is going on inside, from news
stories, for example, the development of the new journaling
file system which is reportedly going on.
The fact of the matter is that major developments require
a lot of synchronized design and planning, and are just not
susceptible to the approach of having lots of people
contributing independently.
Robert Dewar
Ada Core Technologies
Robert Dewar
Ada Core Technologies
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
next prev parent reply other threads:[~1999-03-10 0:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-02 0:00 SGI GNAT Question? (Long) Paul Colvert
1999-03-02 0:00 ` David C. Hoos, Sr.
1999-03-02 0:00 ` GNAT discussions should be here as well kvisko
1999-03-02 0:00 ` Larry Kilgallen
1999-03-02 0:00 ` dennison
1999-03-02 0:00 ` robert_dewar
1999-03-02 0:00 ` Mike Silva
1999-03-02 0:00 ` Samuel Mize
1999-03-02 0:00 ` SGI GNAT Question? (Long) dewar
1999-03-03 0:00 ` Paul Colvert
1999-03-03 0:00 ` robert_dewar
1999-03-04 0:00 ` SpamSpamSpam
1999-03-04 0:00 ` dennison
1999-03-04 0:00 ` dewar
1999-03-05 0:00 ` SpamSpamSpam
1999-03-05 0:00 ` bourguet
1999-03-05 0:00 ` dennison
1999-03-05 0:00 ` dewar
1999-03-05 0:00 ` dewar
1999-03-05 0:00 ` dennison
1999-03-05 0:00 ` robert_dewar
1999-03-07 0:00 ` root
1999-03-07 0:00 ` dewar
1999-03-08 0:00 ` root
1999-03-09 0:00 ` Some GNAT history (was Re: SGI GNAT Question? (Long)) dewar
1999-03-09 0:00 ` dennison
1999-03-09 0:00 ` robert_dewar
1999-03-09 0:00 ` Tom Moran
1999-03-11 0:00 ` Arthur Evans Jr
1999-03-11 0:00 ` dennison
1999-03-09 0:00 ` SGI GNAT Question? (Long) dewar
1999-03-10 0:00 ` SpamSpamSpam
1999-03-10 0:00 ` Chris Morgan
1999-03-10 0:00 ` dewar
1999-03-10 0:00 ` Chris Morgan
1999-03-10 0:00 ` dewar [this message]
1999-03-10 0:00 ` robert_dewar
1999-03-07 0:00 ` David Botton
1999-03-07 0:00 ` robert_dewar
1999-03-05 0:00 ` dennison
1999-03-05 0:00 ` dewar
1999-03-07 0:00 ` root
1999-03-07 0:00 ` dewar
1999-03-08 0:00 ` Marin David Condic
1999-03-05 0:00 ` GNAT Field Test scope (was SGI GNAT Question) Larry Kilgallen
1999-03-02 0:00 ` SGI GNAT Question? (Long) Gautier
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox