From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30194 invoked by alias); 19 Sep 2009 15:58:09 -0000 Received: (qmail 30183 invoked by uid 22791); 19 Sep 2009 15:58:08 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_83 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 19 Sep 2009 15:58:03 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 4913A2BAB2C; Sat, 19 Sep 2009 11:58:02 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Gng+dR7Yr9f1; Sat, 19 Sep 2009 11:58:02 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 0BF732BAB2B; Sat, 19 Sep 2009 11:58:01 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 6CB73F5935; Sat, 19 Sep 2009 08:57:50 -0700 (PDT) Date: Sat, 19 Sep 2009 15:58:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [commit] Fix fnchange.lst Message-ID: <20090919155750.GU8910@adacore.com> References: <831vm3w9ic.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <831vm3w9ic.fsf@gnu.org> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00633.txt.bz2 > Would it be a good idea to run the ARI script when tarring a > pre-release or a release? Too many files were clashing after 8+3 > truncation. I don't think that this _needs_ to be part of the release process. If we monitored the ARI results daily (I think that Pierre is doing that for us right now, but it looks like doschk checks are not included in the email), we shouldn't have this sort of issue. In the meantime, we can just make sure we check the ARI on the web just before we cut the branch, and maybe just before we create the release tarball. If someone extracts out the script that does "dos checking" in the ARI script, and returns a textual list of files that cause problem, I don't mind adding it to the release procedure. -- Joel