From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: --with-pkgversion and --with-bugurl support for GDB
Date: Tue, 20 May 2008 15:25:00 -0000 [thread overview]
Message-ID: <ubq31irlm.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0805191942380.1489@digraph.polyomino.org.uk>
> Date: Mon, 19 May 2008 19:50:42 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: gdb-patches@sourceware.org
>
> I do not see any mention of info-gdb or help-gdb at
> <http://www.gnu.org/software/gdb/mailing-lists/>, so I think that part of
> the information is obsolete.
The right place to check whether these lists exist is
http://lists.gnu.org/mailman/listinfo/. In any case, the text that
referred to these two said NOT to use them.
> 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
> <http://gcc.gnu.org/bugs.html>).
Sorry, I don't agree. I think the manual should have clear
instructions on how to report bugs efficiently. I don't like to ask
users to study Web pages to know that when they are already reading
documentation.
I don't mind removing obsolete information, but please either update
the rest to talk about bug-gdb and gdb@sources.redhat.com, or leave it
intact and I will get to updating it when I have time.
Thanks.
next prev parent reply other threads:[~2008-05-20 3:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 20:46 Joseph S. Myers
2008-05-20 0:05 ` Eli Zaretskii
2008-05-20 3:26 ` Joseph S. Myers
2008-05-20 15:25 ` Eli Zaretskii [this message]
2008-05-20 18:24 ` Joseph S. Myers
2008-05-21 2:54 ` Eli Zaretskii
2008-05-30 15:23 ` Ping " Joseph S. Myers
2008-06-05 20:24 ` Daniel Jacobowitz
2008-06-05 21:28 ` Joseph S. Myers
2008-06-05 21:45 ` Daniel Jacobowitz
2008-06-06 10:21 ` Eli Zaretskii
2008-06-06 20:22 ` Joseph S. Myers
2008-06-06 20:26 ` Daniel Jacobowitz
2008-06-06 20:32 ` Eli Zaretskii
2008-06-10 12:58 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ubq31irlm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox