From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22349 invoked by alias); 19 Sep 2009 17:47:36 -0000 Received: (qmail 22341 invoked by uid 22791); 19 Sep 2009 17:47:36 -0000 X-SWARE-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,BAYES_00,BOTNET,J_CHICKENPOX_83,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 19 Sep 2009 17:47:31 +0000 Received: from conversion-daemon.i-mtaout1.012.net.il by i-mtaout1.012.net.il (HyperSendmail v2007.08) id <0KQ800L00BQORK00@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Sat, 19 Sep 2009 20:47:27 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.173.118]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KQ800EYOC336G80@i-mtaout1.012.net.il>; Sat, 19 Sep 2009 20:47:27 +0300 (IDT) Date: Sat, 19 Sep 2009 17:47:00 -0000 From: Eli Zaretskii Subject: Re: [commit] Fix fnchange.lst In-reply-to: <20090919155750.GU8910@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ws3uvney.fsf@gnu.org> References: <831vm3w9ic.fsf@gnu.org> <20090919155750.GU8910@adacore.com> X-IsSubscribed: yes 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/msg00636.txt.bz2 > Date: Sat, 19 Sep 2009 08:57:50 -0700 > From: Joel Brobecker > Cc: gdb-patches@sourceware.org > > > 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. While it's not fatal to have these issues exist on the trunk during development, having them in a tarball is really bad. That's why I won't even dream of insisting that ARE results are monitored daily. But I do think we should re-check this before a tarball is released. > 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. If Pierre can do that, fine. If not, if someone can tell me where do I download the ARI script, I will give it a try. Thanks.