From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9504 invoked by alias); 19 Mar 2004 17:45:35 -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 9496 invoked from network); 19 Mar 2004 17:45:34 -0000 Received: from unknown (HELO smtp10.atl.mindspring.net) (207.69.200.246) by sources.redhat.com with SMTP; 19 Mar 2004 17:45:34 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1) id 1B4O3i-0008Af-00; Fri, 19 Mar 2004 12:45:26 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 856F74B104; Fri, 19 Mar 2004 12:45:17 -0500 (EST) To: cagney@gnu.org, mec.gnu@mindspring.com Subject: Re: [patch/rfc] Add meaningful section titles to PROBLEMS Cc: gdb-patches@sources.redhat.com Message-Id: <20040319174517.856F74B104@berman.michael-chastain.com> Date: Fri, 19 Mar 2004 17:45:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-03/txt/msg00463.txt.bz2 mec> I'm willing to abide by whatever Eli, the maintainer, decides. ac> I don't know who the maintainer is, however doco and releng should be ac> "on the same page". Well, then I think you need to decide who the maintainer of PROBLEMS is and document that in the MAINTAINERS file. There are no specific entries for "releng" so I presumed they fell under documentation. ac> As I stated in my cover note, gdb/1560 for instance is a regression ac> since GDB _5.0_. Okay, then a user of gdb 6.0 is not going to suffer from additional hurt from gdb/1560 if they upgrade to gdb 6.1. And you are right, it's not a regression from 6.0. ac> Trying to list regressions is of little value. We have different opinions on this. When I upgrade a software package, I find the list of regressions from my current version to be of *great* value. For each new problem, I have to ascertain whether it affects my system. If it affects my system, I have to figure out how to work around the problem. If the problems are too severe, then I know that I am better off not upgrading. ac> Giving this file meaningful titles (so users don't have to wade through ac> irrelevances such as gdb/1512) is a first step. gdb/1512 is a bug in gdb. Naturally, we can describe it so that most people will realize that it won't bother them and can just read through to the next bug. If you claim that gdb/1512 is irrelevant to every user (and I'm almost of that opinion myself), and you can persuade other maintainers of that position, then we can stop testing for it and just PASS those tests. But right now we consider that behavior of gdb to be a bug that needs fixing. Michael C