* binutils.texi (Bug Reporting): Clarify that large files should

	not be sent to bug-gnu-utils.

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 1922b73ba1bcc06cbc0684189e18f3add6e71e64..1e22647bfb56e8f65cfe0edeb5c0f416470e401c 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+1999-08-31  Ian Lance Taylor  <ian@zembu.com>
+
+       * binutils.texi (Bug Reporting): Clarify that large files should
+       not be sent to bug-gnu-utils.
+
 1999-08-28  Stephane Carrez  <stcarrez@worldnet.fr>
 
        * readelf.c (process_extended_line_op): New parameter pointer_size,

diff --git a/binutils/binutils.texi b/binutils/binutils.texi
index 83ab291e3e61aef4952fe439f8a73a1524f436da..6fea8365dc22f3c26c6e93e2aae88935c8f83832 100644 (file)
--- a/binutils/binutils.texi
+++ b/binutils/binutils.texi
@@ -2841,9 +2841,10 @@ and then we might not encounter the bug.
 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.  Making them available
-for anonymous FTP is not as good, but may be the only reasonable choice
-for large object files.
+necessary to get them through the mail system.  Note that
+@samp{bug-gnu-utils@@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.
 
 If the source files were produced exclusively using @sc{gnu} programs
 (e.g., @code{gcc}, @code{gas}, and/or the @sc{gnu} @code{ld}), then it