From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [5.2:rfa/doc] Mention http://www.gnu.org/software/gdb/bugs/
Date: Thu, 28 Mar 2002 17:46:00 -0000 [thread overview]
Message-ID: <3CA3C6ED.9060506@cygnus.com> (raw)
In-Reply-To: <3CA3A4E1.3060704@cygnus.com>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
> Hello,
>
> The attached patch updates gdb/README and gdb/doc/gdb.texinfo to both mention the web pages and prefer them over the e-mail address when reporting bugs.
>
> The attached is against the branch, the trunk will need @smallexample.
>
> ok?
> Andrew
Doh! Attached.
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 4557 bytes --]
2002-03-28 Andrew Cagney <ac131313@redhat.com>
* README (Reporting Bugs in GDB): Document the bug web page as the
prefered way of submitting bugs.
Fix PR gdb/402.
Index: doc/ChangeLog
2002-03-28 Andrew Cagney <ac131313@redhat.com>
* gdb.texinfo (Bug Reporting): Document that the web is the
prefered way of submitting bug reports.
(Bug Reporting): Delete the s-mail address as the last resort.
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.17
diff -u -r1.17 README
--- README 2002/02/23 20:59:55 1.17
+++ README 2002/03/28 20:11:05
@@ -2,14 +2,18 @@
Updated 23 January, 2002 by Andrew Cagney
This is GDB, the GNU source-level debugger.
-A summary of new features is in the file `NEWS'.
-See the GDB home page at http://www.gnu.org/software/gdb/ for up to
-date release information, mailing list links and archives, etc.
+A summary of new features is in the file `gdb/NEWS'.
-See the file PROBLEMS for late breaking news.
+The GDB home page at http://www.gnu.org/software/gdb/ for up to date
+release information, mailing list links and archives, etc.
+The file `gdb/PROBLEMS' contains information on problems identified
+late in the release cycle. GDB's bug tracking data base at
+http://www.gnu.org/software/gdb/bugs/ contains a more complete list of
+bugs.
+
Unpacking and Installation -- quick overview
==========================
@@ -479,23 +483,28 @@
not a complete solution. You will need something on the other end
that also speaks UDI.
+
+Reporting Bugs in GDB
+=====================
+
+ There are several ways of reporting bugs in GDB. The prefered
+method is to use the World Wide Web:
+
+ http://www.gnu.org/software/gdb/bugs/
-Reporting Bugs
-===============
+As an alternative, the bug report can be submitted, via e-mail, to the
+address "bug-gdb@gnu.org".
- The correct address for reporting bugs found in gdb is
-"bug-gdb@gnu.org". Please email all bugs, and all requests for help
-with GDB, to that address. Please include the GDB version number
-(e.g., gdb-5.1.1), and how you configured it (e.g., "sun4" or "mach386
-host, i586-intel-synopsys target"). Since GDB now supports so many
+ When submitting a bug, please include the GDB version number (e.g.,
+gdb-5.1.1), and how you configured it (e.g., "sun4" or "mach386 host,
+i586-intel-synopsys target"). Since GDB now supports so many
different configurations, it is important that you be precise about
this. If at all possible, you should include the actual banner that
GDB prints when it starts up, or failing that, the actual configure
command that you used when configuring GDB.
- For more information on how/whether to report bugs, see the GDB
-Bugs section of the GDB manual (gdb/doc/gdb.texinfo) or the
-gdb/CONTRIBUTE file.
+ For more information on how/whether to report bugs, see the
+Reporting Bugs chapter of the GDB manual (gdb/doc/gdb.texinfo.
Graphical interface to GDB -- X Windows, MS Windows
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.92
diff -u -r1.92 gdb.texinfo
--- gdb.texinfo 2002/02/24 17:18:25 1.92
+++ gdb.texinfo 2002/03/28 20:11:24
@@ -13497,13 +13497,17 @@
distribution.
@c should add a web page ref...
-In any event, we also recommend that you send bug reports for
-@value{GDBN} to this addresses:
+In any event, we also recommend that you submit bug reports for
+@value{GDBN}. The prefered method is to submit them directly using the
+World Wide Web, see:
@example
-bug-gdb@@gnu.org
+@uref{http://www.gnu.org/software/gdb/bugs/}
@end example
+@noindent
+Alternatively, the e-mail address @email{bug-gdb@@gnu.org} 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
@@ -13517,16 +13521,6 @@
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.
-
-As a last resort, send bug reports on paper to:
-
-@example
-@sc{gnu} Debugger Bugs
-Free Software Foundation Inc.
-59 Temple Place - Suite 330
-Boston, MA 02111-1307
-USA
-@end example
The fundamental principle of reporting bugs usefully is this:
@strong{report all the facts}. If you are not sure whether to state a
next prev parent reply other threads:[~2002-03-29 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 15:20 Andrew Cagney
2002-03-28 17:46 ` Andrew Cagney [this message]
2002-03-28 23:23 ` Eli Zaretskii
2002-04-07 12:06 ` Andrew Cagney
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=3CA3C6ED.9060506@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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