aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@dcc.unicamp.br>1998-12-06 02:01:26 +0000
committerAlexandre Oliva <oliva@gcc.gnu.org>1998-12-06 02:01:26 +0000
commitbadcf9162061ffc55860447d372eeb982fa0c2e4 (patch)
tree6076a4e921c7e03c15a2d6c29748451fbf01fde6
parent892d0a6dfc69e07739dc787429f9638a5073d8e0 (diff)
downloadgcc-badcf9162061ffc55860447d372eeb982fa0c2e4.zip
gcc-badcf9162061ffc55860447d372eeb982fa0c2e4.tar.gz
gcc-badcf9162061ffc55860447d372eeb982fa0c2e4.tar.bz2
gcc.texi (Bug Reporting): 40Kb is a soft limit, larger compressed reports are ok and preferred over URLs
* gcc.texi (Bug Reporting): 40Kb is a soft limit, larger compressed reports are ok and preferred over URLs From-SVN: r24126
-rw-r--r--gcc/ChangeLog5
-rw-r--r--gcc/gcc.texi9
2 files changed, 12 insertions, 2 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index c1250f2..8cb3bb0 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+Sun Dec 6 07:49:29 1998 Alexandre Oliva <oliva@dcc.unicamp.br>
+
+ * gcc.texi (Bug Reporting): 40Kb is a soft limit, larger
+ compressed reports are ok and preferred over URLs
+
Sun Dec 6 07:45:33 1998 Alexandre Oliva <oliva@dcc.unicamp.br>
* invoke.texi (Warning Options): Soften the tone of -pedantic
diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index b0fee64..bf454e1 100644
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2252,9 +2252,14 @@ 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 limit on the
+@code{MIME} or @code{uuencode}. There is a 40k message soft limit on the
@samp{egcs-bugs@@cygnus.com} mailing list at the time of this writing
-(August 1998).
+(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.
To enable someone to investigate the bug, you should include all these
things: