From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29808 invoked by alias); 3 Apr 2004 01:19:10 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29794 invoked from network); 3 Apr 2004 01:19:09 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 3 Apr 2004 01:19:09 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1B9ZoS-0001BW-00; Fri, 02 Apr 2004 20:19:08 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 93EC34B104; Fri, 2 Apr 2004 20:19:32 -0500 (EST) To: cagney@gnu.org, gdb-patches@sources.redhat.com, gdb@sources.redhat.com Subject: Re: GDB 6.1 branch FROZEN Message-Id: <20040403011932.93EC34B104@berman.michael-chastain.com> Date: Sat, 03 Apr 2004 01:19:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-04/txt/msg00021.txt.bz2 Andrew Cagney writes: > My intention is to let the snapshot process churn something out > "tonight", followed by a 6.1 candidate sometime "tomorrow". I'm publishing my next spin on i686-pc-linux-gnu about 30-40 hours from now. This includes gdb 6.0.91. I'll be sure to test the 6.1 candidate on hppa2.0w-hp-hpux11.11 a few hours after it comes out. I can do something on i686-pc-linux-gnu as well. I just got word back from a user that 6.0.91 does not build on the user's hppa2.0w-hp-hpux11.00 system (pr gdb/1458). Michael C