OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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
This commit is contained in:
Alexandre Oliva 1998-12-06 02:01:26 +00:00 committed by Alexandre Oliva
parent 892d0a6dfc
commit badcf91620
2 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -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

9
gcc/gcc.texi
View File

@ -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: