MatCat.OpenSource/8sa1-binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update address for bug reports.

Browse Source
This commit is contained in:
Phil Blundell 2001-01-07 15:04:21 +00:00
parent 5ad083e32d
commit 2f952d2010
3 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
binutils/ChangeLog
View File

@ -1,3 +1,9 @@
2001-01-07 Philip Blundell <philb@gnu.org>
* binutils.texi (Bug Reporting): Replace `bug-gnu-utils' with
`bug-binutils'.
* README: Likewise.
2000-12-19 Nick Clifton <nickc@redhat.com>
* dlltool.c: Add missing support for arm-epoc-pe.

2
binutils/README
View File

@ -111,7 +111,7 @@ with gdb-4.x) may also be of help.
Reporting bugs
==============
Send bug reports and patches to bug-gnu-utils@gnu.org. Always mention
Send bug reports and patches to bug-binutils@gnu.org. Always mention
the version number you are running; this is printed by running any of
the binutils with the --version option. We appreciate reports about
bugs, but we do not promise to fix them.

4
binutils/binutils.texi
View File

@ -2900,7 +2900,7 @@ individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
distribution.
In any event, we also recommend that you send bug reports for the binary
utilities to @samp{bug-gnu-utils@@gnu.org}.
utilities to @samp{bug-binutils@@gnu.org}.
The fundamental principle of reporting bugs usefully is this:
@strong{report all the facts}. If you are not sure whether to state a
@ -2961,7 +2961,7 @@ A complete input file, or set of input files, that will reproduce the
bug. If the utility is reading an object file or files, then it is
generally most helpful to send the actual object files, uuencoded if
necessary to get them through the mail system. Note that
@samp{bug-gnu-utils@@gnu.org} is a mailing list, so you should avoid
@samp{bug-binutils@@gnu.org} is a mailing list, so you should avoid
sending very large files to it. Making the files available for
anonymous FTP is OK.