From: <guerby@acm.org>
To: jsm28@cam.ac.uk
Cc: schwab@suse.de, gcc@gcc.gnu.org
Subject: Re: gcc-ss-20011203 is now available
Date: Tue, 04 Dec 2001 12:16:00 -0000 [thread overview]
Message-ID: <200112042006.fB4K6YG30195@ulmo.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0112041556420.14880-100000@kern.srcf.societies.cam.ac.uk> (jsm28@cam.ac.uk)
> In the middle of a series of 19 checkins, you mean
May be the snapshot script could use a stable checkout, if
the script is using contrib/gcc_build checkout I can propose
a patch to implement a stable-checkout option. Algorithm:
checkout
for I in 1 .. MAX loop
wait X
update
exit when no files updated
end loop
With X being something like 10 or 15 minutes, it should be *very*
unlikely to get something inconsistent due to a serie of checkins, and
it would probably also survive an ooops commit / revert cycle, at the
cost of some wait. MAX could be set so that X * MAX < time between
automatic run / 2.
--
Laurent Guerby <guerby@acm.org>
next prev parent reply other threads:[~2001-12-04 20:16 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 [this message]
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 ` 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=200112042006.fB4K6YG30195@ulmo.localdomain \
--to=guerby@acm.org \
--cc=gcc@gcc.gnu.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).