From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20693 invoked by alias); 4 Dec 2001 20:24:29 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 20639 invoked from network); 4 Dec 2001 20:24:25 -0000 Received: from unknown (HELO puce.csi.cam.ac.uk) (131.111.8.40) by sources.redhat.com with SMTP; 4 Dec 2001 20:24:25 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by puce.csi.cam.ac.uk with esmtp (Exim 3.22 #1) id 16BM71-0001LM-00; Tue, 04 Dec 2001 20:24:19 +0000 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.12 #1 (Debian)) id 16BM70-0006ut-00; Tue, 04 Dec 2001 20:24:18 +0000 Date: Tue, 04 Dec 2001 12:24:00 -0000 From: "Joseph S. Myers" X-X-Sender: To: cc: , Subject: Re: gcc-ss-20011203 is now available In-Reply-To: <200112042006.fB4K6YG30195@ulmo.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-12/txt/msg00154.txt.bz2 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