Stable release?

[Per Bothner]

Matt Welsh <mdw@cs.berkeley.edu> writes:

> the point is that we can't wait for the EGCS team to decide that the
> whole damn compiler is ready for a release.)  ...  Also keep in mind
> that almost all of the bugs we're likely to run into are in libgcj,
> NOT EGCS! The point of having a "branded" snapshot of EGCS ...

There is no "egcs team" - it's the "gcc team".  There will never be
another egcs release, only gcc releases.  The cvs tree is rooted at
"egcs" only because fixing it would mean everybody's checked-out
cvs tree would break.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/