From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21629 invoked by alias); 22 Aug 2003 18:40:56 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 21621 invoked from network); 22 Aug 2003 18:40:55 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 22 Aug 2003 18:40:55 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id CF6C32B7F; Fri, 22 Aug 2003 14:40:54 -0400 (EDT) Message-ID: <3F4663B6.7000700@redhat.com> Date: Fri, 22 Aug 2003 18:40:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: drow@mvista.com, gdb-patches@sources.redhat.com Subject: Re: [commit] Last major piece of fork tracing - vfork/exec References: <200308221553.h7MFrP2p013327@duracef.shout.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00398.txt.bz2 > I hate to cause trouble here. We're all on edge with the release > coming up (and this is also end-of-quarter for the red hat people). > But I have to speak up. (I never no when EOQ is so thanks for the heads up). > The release is already being held up for the gdb.c++ -> gdb.cp > renaming. The one-week comment period for that change ends this > afternoon. Then I can commit this change to gdb HEAD. Then it > needs a shakedown period in gdb HEAD. Then I can commit the > change to gdb gdb_6_0-branch, and it will need a shakedown period > there as well. The shake down will be telling people to do a cvs update -d src/gdb/testsuite/gdb.cp. > Andrew, I'm frankly amazed that you decided this feature was > release critical, but that's okay. My role is to get it into > the branch expeditiously. The release isn't been held up for the gdb.cp rename, it happened to slip nicely into the schedule. If it's not done by Sunday, I can easily do it myself. The bottom line is that if it screws up, and the testsuite is a brick, no one will notice. GDB on GNU/Linux will still work. On the other hand, if vfork/exec breaks, GNU/Linux breaks and everyone notices. Andrew