From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18995 invoked by alias); 11 Feb 2002 17:24:49 -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 18572 invoked from network); 11 Feb 2002 17:24:12 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.135.44) by sources.redhat.com with SMTP; 11 Feb 2002 17:24:12 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id B5BC53CC2; Mon, 11 Feb 2002 12:24:09 -0500 (EST) Message-ID: <3C67FE39.9000700@cygnus.com> Date: Mon, 11 Feb 2002 09:24:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: gdb@sources.redhat.com Subject: Re: When may I close a 5.1.1 PR? References: <200202110204.g1B24xf08198@duracef.shout.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00177.txt.bz2 > So last week I filed this PR: > > http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=334 > > This is a test failure in 5.1.1, but it is fixed in gdb HEAD (the mainline). > > As a general question, when is a good time to close a PR that is fixed > in the mainline but not in the 5.1 branches: > > . after gdb 5.2 is released? > . after gdb 5.2 is branched? > . as soon as the bug is fixed in mainline? > > I'll be happy to do whatever the voices in my mailbox tell me. :) I'm just happy to see the problem and fix recorded. Probably close it since I assume no one has any intention of fixing it on the branch. -- As an aside, I've been wondering what to do with the page: http://sources.redhat.com/gdb/bugs/ I was thinking that it should just jump to the bug database. However, looking around I've noticed that other projects have (for an equivalent page) used it to ``educate'' the reader as to how to submit a better bug report and where to find potential fixes.. I'm not sure we want to go down that path. However, having the gdb/bugs/ page draw peoples attention to the current sources (http://sources.redhat.com/gdb/current) could help. thoughts? Andrew