public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David O'Brien" <obrien@FreeBSD.org>
To: Bernd Schmidt <bernds@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: making a 2.95.4 release
Date: Thu, 28 Mar 2002 12:14:00 -0000	[thread overview]
Message-ID: <20020328115609.E90592@dragon.nuxi.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203281939380.20175-100000@host140.cambridge.redhat.com>; from bernds@redhat.com on Thu, Mar 28, 2002 at 07:46:36PM +0000

On Thu, Mar 28, 2002 at 07:46:36PM +0000, Bernd Schmidt wrote:
> > Why couldn't Red Hat do that in the EGCS 1.0 days?
> 
> Do what, exactly?

Why couldn't Red Hat use EGCS 1.0.2 + patches.  Instead EGCS 1.0.3 as
released for Red Hat's needs.
    http://gcc.gnu.org/egcs-1.0/egcs-1.0.3.html
    EGCS 1.0.3 is a minor update to the EGCS 1.0.2 compiler to fix a few
    problems reported by Red Hat for builds of Red Hat 5.1.


> > Does Red Hat and glibc carry more stock than Debian, FreeBSD, NetBSD,
> > OpenBSD combined?
> 
> Not sure how Red Hat factors into the equation, since our OS people are
> no longer using 2.95.x.

See above.  It factors in because a need of Red Hat was the reason for a
release from what was suppose to be a "dead" branch.


> I thought you are shipping a separate set of gcc sources for BSD - so
> where's the problem with just using code from the branch for that?  I fail
> to see how making it an official release would be of any help.

Ok, but then I will call it 2.95.4 and I don't want any crap for using a
non-"real" version number.  Also I will have to move our port to using
CVS for distfile fetching as when we switch to 3.1, about 1/2 of the 6000
3rd party apps will not compile with 3.1.  Thus they will have to depend
our our gcc295 port.

Making a 2.95.4 release also helps the other people out there that are
still using 2.95.3 get a few bug fixes.


> There needs to be more testing to make
> sure there are no regressions, and it could be difficult to find the
> volunteers for that with 3.1 around the corner.  And if we make another
> official release, I simply think it would be nice to fix more problems
> first.

Fixing more problems would be nice, but will people make any more commits
to the 2.95 branch?

-- 
-- David  (obrien@FreeBSD.org)

  reply	other threads:[~2002-03-28 19:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28  9:35 David O'Brien
2002-03-28  9:39 ` law
2002-03-28  9:58 ` Gerald Pfeifer
2002-04-02  1:09   ` Gerald Pfeifer
2002-04-02 10:51     ` Joe Buck
2002-03-28 10:19 ` Bernd Schmidt
2002-03-28 11:38   ` David O'Brien
2002-03-28 11:46     ` Philip Blundell
2002-03-28 12:10       ` David O'Brien
2002-03-28 12:22         ` Daniel Jacobowitz
2002-03-28 11:57     ` Daniel Jacobowitz
2002-03-28 11:58     ` Bernd Schmidt
2002-03-28 12:14       ` David O'Brien [this message]
2002-03-28 12:29         ` Bernd Schmidt
2002-03-28 13:26         ` law
2002-04-03  2:57   ` Wolfram Gloger
2002-03-31  6:48 ` Richard Zidlicky
2002-03-31 12:14 Erik Schnetter

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=20020328115609.E90592@dragon.nuxi.com \
    --to=obrien@freebsd.org \
    --cc=bernds@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /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).