public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: "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 12:46:00 -0000	[thread overview]
Message-ID: <20011204155032.A24992@disaster.jaj.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112042032530.27017-100000@kern.srcf.societies.cam.ac.uk>; from jsm28@cam.ac.uk on Tue, Dec 04, 2001 at 08:36:41PM +0000

On Tue, Dec 04, 2001 at 08:36:41PM +0000, Joseph S. Myers wrote:
> On Tue, 4 Dec 2001, Phil Edwards wrote:
> > if TIME near Sunday 4:40 PM Pacific timezone
> 
> Monday.

Thinko.

> > Doesn't gcc_release do a build in order to ensure the generated source
> > files are there?  It's certainly no guarantee, but it should prevent
> > snapshots from going out that don't build on, say, i596-linux.
> 
> It only does a build for releases, not snapshots.  Given the load on 
> gcc.gnu.org, doing a build for snapshots does not seem wise.

Ah, okay.  Maybe once the pserver load is off to some other machine.
But then there sre still...

> Besides, patching generated files that aren't in CVS doesn't really work
> well - there isn't a "release mode" for gcc_update that will clean up
> timestamps on (say) Bison-generated files after applying a patch, despite
> those files being in CVS and so not meant to be touched for CVS checkouts.
> 
> Including Info and Bison-generated files would also substantially bulk up 
> diffs.

...these issues.  Hmmm.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2001-12-04 20:46 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 [this message]
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           ` gcc-ss-20011203 is now available Mark Mitchell
2001-12-04  8:17 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=20011204155032.A24992@disaster.jaj.com \
    --to=pedwards@disaster.jaj.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.org \
    --cc=jsm28@cam.ac.uk \
    --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).