This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.4.0 Status Report (2009-03-13)
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, "bonzini at gnu dot org" <bonzini at gnu dot org>, "dave dot korn dot cygwin at googlemail dot com" <dave dot korn dot cygwin at googlemail dot com>, "dberlin at dberlin dot org" <dberlin at dberlin dot org>, "dje dot gcc at gmail dot com" <dje dot gcc at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "law at redhat dot com" <law at redhat dot com>, "mark at codesourcery dot com" <mark at codesourcery dot com>, "rguenther at suse dot de" <rguenther at suse dot de>, "stevenb dot gcc at gmail dot com" <stevenb dot gcc at gmail dot com>
- Date: Mon, 23 Mar 2009 00:25:35 -0700
- Subject: Re: GCC 4.4.0 Status Report (2009-03-13)
- References: <49C58A77.3000805@codesourcery.com> <4aca3dc20903211937k29299a7co9bf4add50a050f71@mail.gmail.com> <20090322050024.GA18893@synopsys.com> <4aca3dc20903220547v8923d55v9ac593f8400be6a9@mail.gmail.com> <10903221258.AA04666@vlsi1.ultra.nyu.edu> <206fcf960903220718oefa452ek60dcc1d933e1e093@mail.gmail.com> <10903221441.AA05218@vlsi1.ultra.nyu.edu> <206fcf960903220808w4c04c0e9g74b25a55ea3d8b42@mail.gmail.com> <20090323063854.GB22165@synopsys.com> <b609cb3b0903222352i3800ce8apc97d6ef026199105@mail.gmail.com>
On Mon, Mar 23, 2009 at 2:38 AM, Joe Buck <Joe.Buck@synopsys.com> wrote:
> > GCC uses are the ones developed in the egcs days. Remember the old
> > days when the location of the development tree and the snapshots was
> > a secret, and people were threatened with banning if they let it out?
On Sun, Mar 22, 2009 at 11:52:25PM -0700, NightStrike wrote:
> Are you serious? Why would it be handled that way?
Yes, I'm serious; it was a hidden directory on vger.rutgers.edu, and the
README file in the directory contained the banning threat, though as far
as I know the threat was never actually carried out.
As for why, I don't know. Maybe Kenner has some idea.