From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <guerby@acm.org>
Cc: <schwab@suse.de>, <gcc@gcc.gnu.org>
Subject: Re: gcc-ss-20011203 is now available
Date: Tue, 04 Dec 2001 12:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112042018200.24875-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200112042006.fB4K6YG30195@ulmo.localdomain>
On Tue, 4 Dec 2001 guerby@acm.org wrote:
> > 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:
It is maintainer-scripts/gcc_release, it tags the snapshot (which takes
over ten minutes - this is a heavily loaded machine and tagging involves
writing to all files in the tree) then checks out on the tag (also slow).
The established practice is that snapshots may sometimes be broken and
people using them should just wait for the next snapshot in that case.
However, it helps everyone using CVS if people (a) scrupulously test their
patches following the instructions, including on multiple platforms for
anything potentially destabilising and (b) check in all files that are
part of a patch, and only those files, having verified that the output of
cvs diff on those files includes the intended changes and no others, with
a single commit command naming those files, if possible.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-12-04 20:24 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 [this message]
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=Pine.LNX.4.33.0112042018200.24875-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.org \
--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).