From: "David O'Brien" <obrien@FreeBSD.org>
To: Philip Blundell <pb@nexus.co.uk>
Cc: Bernd Schmidt <bernds@redhat.com>, gcc@gcc.gnu.org
Subject: Re: making a 2.95.4 release
Date: Thu, 28 Mar 2002 12:10:00 -0000 [thread overview]
Message-ID: <20020328114900.C90592@dragon.nuxi.com> (raw)
In-Reply-To: <1017343277.384.13.camel@kc>; from pb@nexus.co.uk on Thu, Mar 28, 2002 at 07:21:16PM +0000
On Thu, Mar 28, 2002 at 07:21:16PM +0000, Philip Blundell wrote:
> On Thu, 2002-03-28 at 18:18, David O'Brien wrote:
> > Does Red Hat and glibc carry more stock than Debian, FreeBSD, NetBSD,
> > OpenBSD combined?
>
> To be fair, from Debian's point of view a 2.95.4 release would make
> virtually no practical difference. The source tarball we currently use
> is essentially a snapshot from the top of the 2.95 branch in CVS, and we
> apply a whole pile of Debian-specific patches anyway, so it makes no
> real odds to us whether it's annointed as an FSF release or not.
Debian should probably not be calling its GCC "2.95.4" as that confuses
things as Red Hat's "2.96" did. Having an offical 2.95.4 release would
legitimize the version of Debian GCC.
--
-- David (obrien@FreeBSD.org)
next prev parent reply other threads:[~2002-03-28 19:50 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 [this message]
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
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=20020328114900.C90592@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=bernds@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pb@nexus.co.uk \
/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).