X

        * gcc.texi: Update bug reporting instructions to match
        current ezmlm list reality.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@25681 138bc75d-0d04-0410-961f-82ee72b054a4

1 files changed, 9 insertions, 8 deletions

diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 547c7938a3e..7f4b767470c 100644
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2258,14 +2258,15 @@ If you include source code in your message, you can send it as clear
 text if it is small. If the message is larger, you may compress it using
 @file{gzip}, @file{bzip2}, or @file{pkzip}. Please be aware that sending
 compressed files needs an additional binary-safe mechanism such as
-@code{MIME} or @code{uuencode}. There is a 40k message soft limit on the
-@samp{egcs-bugs@@egcs.cygnus.com} mailing list at the time of this writing
-(August 1998).  However, if you can't reduce a bug report to less than
-that, post it anyway; it will be manually approved as long as it is
-compressed. Don't think that posting a URL to the code is better, we do
-want to archive bug reports, and not all maintainers have good network
-connectivity to download large pieces of software when they need them;
-it's much easier for them to have them in their mailboxes.
+@code{MIME} or @code{uuencode}. There is a 100k message limit on the
+@samp{egcs-bugs@@egcs.cygnus.com} mailing list at the time of this
+writing (March 1999).  We're trying to create some mechanism for larger
+bug reports to be submitted; please check the on-line FAQ for more
+up-to-date instructions.  Don't think that just posting a URL to the
+code is better, we do want to archive bug reports, and not all
+maintainers have good network connectivity to download large pieces of
+software when they need them; it's much easier for them to have them in
+their mailboxes.
 
 To enable someone to investigate the bug, you should include all these
 things: