public inbox for gcc-announce@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: gcc-announce@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: GCC 3.3 Prerelease
Date: Tue, 06 May 2003 18:28:00 -0000	[thread overview]
Message-ID: <1052239340.2636.129.camel@doubledemon.codesourcery.com> (raw)
In-Reply-To: <20030506093345.A14675@synopsys.com>

On Tue, 2003-05-06 at 09:33, Joe Buck wrote:
> On Tue, May 06, 2003 at 09:17:27AM -0700, Mark Mitchell wrote:
> > The first GCC 3.3 prerelease is available on gcc.gnu.org:
> > 
> >   ftp://gcc.gnu.org/pub/gcc/snapshots/gcc-*-3.3-20030506.tar.gz

Remember how I said "and correct packaging problems?"

Well, we've got one -- some of the prerelease tarfiles are empty.

New tarfiles will be available as fast as the network can copy them
there.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

      parent reply	other threads:[~2003-05-06 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 16:25 Mark Mitchell
     [not found] ` <20030506093345.A14675@synopsys.com>
2003-05-06 18:28   ` Mark Mitchell [this message]

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=1052239340.2636.129.camel@doubledemon.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc-announce@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    /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).