public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Phil Edwards <pedwards@disaster.jaj.com>,
	"Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: guerby@acm.org, schwab@suse.de, gcc@gcc.gnu.org
Subject: Re: gcc-ss-20011203 is now available
Date: Tue, 04 Dec 2001 19:54:00 -0000	[thread overview]
Message-ID: <6910000.1007519297@localhost> (raw)
In-Reply-To: <20011204153416.A24659@disaster.jaj.com>


> Doesn't gcc_release do a build in order to ensure the generated source
> files are there?

Yes.

I added this both to reduce the amount of logic necessary to create
releases and also as a final sanity check.  The script does a full
bootstrap.

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

  parent reply	other threads:[~2001-12-05  3:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 19:13 gccadmin
2001-12-04  7:11 ` Andreas Schwab
2001-12-04  7:59   ` Joseph S. Myers
2001-12-04 12:16     ` guerby
2001-12-04 12:24       ` Joseph S. Myers
2001-12-04 12:30         ` Phil Edwards
2001-12-04 12:36           ` Joseph S. Myers
2001-12-04 12:46             ` Phil Edwards
2001-12-04 12:50               ` Assembly in Gcc Mark Cuss
2001-12-04 13:03                 ` Graham Stott
2001-12-04 13:27                   ` Mark Cuss
2001-12-04 19:00                   ` Tim Prince
2001-12-11 11:14                   ` Embedded Assembly and MMX in GCC Mark Cuss
2001-12-11 12:35                     ` Alexandre Oliva
2001-12-11 13:00                       ` Mark Cuss
2001-12-11 13:18                         ` Alexandre Oliva
2001-12-11 14:09                           ` Mark Cuss
2001-12-12  3:48                       ` Andreas Schwab
2001-12-11 14:38                     ` Craig Rodrigues
2001-12-04 19:54           ` Mark Mitchell [this message]
2001-12-04  8:17 gcc-ss-20011203 is now available Richard Kenner
2001-12-04  8:32 ` Andreas Schwab

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=6910000.1007519297@localhost \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.org \
    --cc=jsm28@cam.ac.uk \
    --cc=pedwards@disaster.jaj.com \
    --cc=schwab@suse.de \
    /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).