From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17642 invoked by alias); 18 Mar 2004 06:06:53 -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 17633 invoked from network); 18 Mar 2004 06:06:52 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 18 Mar 2004 06:06:52 -0000 Received: from [207.232.27.5] (helo=WST0054) by monty-python.gnu.org with asmtp (Exim 4.30) id 1B3qbd-0004Zs-E6; Thu, 18 Mar 2004 01:02:13 -0500 Date: Thu, 18 Mar 2004 06:06:00 -0000 Message-ID: From: Eli Zaretskii To: David Carlton CC: mec.gnu@mindspring.com,gdb-patches@sources.redhat.com In-reply-to: (message from David Carlton on Wed, 17 Mar 2004 11:48:56 -0800) Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0 Reply-to: Eli Zaretskii References: <20040317193026.112C44B104@berman.michael-chastain.com> X-SW-Source: 2004-03.o/txt/msg00419.txt Message-ID: <20040318060600.nxWR0s5jD1MYuvzraFTw2mFggbBW9OSPF6GDkGDt8jA@z> > From: David Carlton > Date: Wed, 17 Mar 2004 11:48:56 -0800 > > I think one of the things that is bothering me is that we're > highlighting new bugs but not highlighting bugs that have been fixed. Fixed bugs that we want to tell users about should be in NEWS. > Some of the latter is in NEWS, but NEWS is both at a higher level (it > doesn't mention specific PR numbers) and it tends to concentrate on > new features, which isn't quite the same thing. There's nothing to prevent us from adding fixed bugs to NEWS, I think. However, if the number of bugs fixed between releases is very large, it could make sense not to mention them at all. One case in point is Emacs: its NEWS contains only new and improved features, while the fixed bugs are not mentioned at all, their number being too huge. > For GCC releases, > Gerald Pfeifer (if I'm remembering correctly) goes through the list of > GCC bugs and provides a table of all of the ones that have been fixed > in that particular release (breaking them down into categories); > besides making GCC developers feel good, it can also help users decide > when to upgrade, because they can look at the list of bugs that have > been fixed in the categories that they care about and see how > important those bugs are to them. I sincerely doubt that the list of GCC fixed bugs helps anyone beyond GCC developers and people with special interest in compiler development, as most of them are worded in a way that leaves users with a ``Huh?'' after-taste.