From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13440 invoked by alias); 19 May 2008 19:51:20 -0000 Received: (qmail 13430 invoked by uid 22791); 19 May 2008 19:51:19 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 19 May 2008 19:50:44 +0000 Received: (qmail 24726 invoked from network); 19 May 2008 19:50:43 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 19 May 2008 19:50:43 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.68) (envelope-from ) id 1JyBNa-0000Wf-0x; Mon, 19 May 2008 19:50:42 +0000 Date: Tue, 20 May 2008 03:26:00 -0000 From: "Joseph S. Myers" To: Eli Zaretskii cc: gdb-patches@sourceware.org Subject: Re: --with-pkgversion and --with-bugurl support for GDB In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00578.txt.bz2 On Mon, 19 May 2008, Eli Zaretskii wrote: > > +@ifset BUGURL > > In any event, we also recommend that you submit bug reports for > > -@value{GDBN}. The preferred method is to submit them directly using > > -@uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web > > -page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can > > -be used. > > - > > -@strong{Do not send bug reports to @samp{info-gdb}, or to > > -@samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do > > -not want to receive bug reports. Those that do have arranged to receive > > -@samp{bug-gdb}. > > - > > -The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which > > -serves as a repeater. The mailing list and the newsgroup carry exactly > > -the same messages. Often people think of posting bug reports to the > > -newsgroup instead of mailing them. This appears to work, but it has one > > -problem which can be crucial: a newsgroup posting often lacks a mail > > -path back to the sender. Thus, if we need to ask for more information, > > -we may be unable to reach you. For this reason, it is better to send > > -bug reports to the mailing list. > > +@value{GDBN} to @value{BUGURL}. > > +@end ifset > > Why do you want to remove all this stuff? If you don't want it under > BUGURL/VERSION_PACKAGE (whose utility, I must admit, I don't fully > understand), then please leave it alone when BUGURL is NOT set. If > you _really_ think it's a good idea to remove this text > unconditionally, please at least tell why you think so. The only case when BUGURL is not set is when someone has used --without-bugurl, which has the specific effect of disabling bug reporting information. By default, it's set to http://www.gnu.org/software/gdb/bugs/ - that's the effect of ACX_BUGURL, the default URL is passed to it. I do not see any mention of info-gdb or help-gdb at , so I think that part of the information is obsolete. It also appears that, in practice, little use is made of bug-gdb and the bug database is the recommended approach. Thus, it seems to me that the appropriate default is to refer to whatever BUGURL is, which by default is the web page where further information is present about information to put in bug reports, and which may be configured by any distributor to point to their own bug database. Should we wish to document alternative methods for reporting bugs in FSF GDB, or to add information or caveats about those methods, I think the right approach is to add the information to that web page (GCC for example has a very extensive web page with instructions at ). This means the useful part of the information in the manual is the pointer to the web page. -- Joseph S. Myers joseph@codesourcery.com