From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16911 invoked by alias); 15 May 2003 22:18:03 -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 16904 invoked from network); 15 May 2003 22:18:02 -0000 Received: from unknown (HELO rose.csi.cam.ac.uk) (131.111.8.13) by sources.redhat.com with SMTP; 15 May 2003 22:18:02 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by rose.csi.cam.ac.uk with esmtp (Exim 4.12) id 19GR31-0001Rn-00; Thu, 15 May 2003 23:17:59 +0100 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.35 #1 (Debian)) id 19GR31-000475-00; Thu, 15 May 2003 23:17:59 +0100 Date: Thu, 15 May 2003 22:18:00 -0000 From: "Joseph S. Myers" X-X-Sender: jsm28@kern.srcf.societies.cam.ac.uk To: Gerald Pfeifer cc: Jie Zhang , Mark Mitchell , gcc@gcc.gnu.org Subject: Re: GCC 3.3 Released In-Reply-To: Message-ID: References: <200305142345.h4ENjScJ002366@doubledemon.codesourcery.com> <3EC31DB2.3090300@magima.com.cn> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-05/txt/msg01557.txt.bz2 On Thu, 15 May 2003, Gerald Pfeifer wrote: > Mark, I have not tested the patch below, because I'm afraid of wreaking > havoc, but this (or a slight variation thereof) should address the problem. You can test this sort of thing against an rsynced copy of the repository (so it needn't wait for 3.4 to come into effect, or require any artificial extra entries on the release instructions). > + # Update this ChangeLog file only if it does not yet contain the > + # entry we are going to add. (This is a safety net for repeated > + # runs of this script for the same release.) > + if [ ! grep "GCC ${RELEASE} released." ${x} ]; then > + cat - ${x} > ${x}.new <