Re: egcs-1.1.2 bug report

[craig at jcb-sc dot com]

Just FYI: I don't run *any* automatic decoder on incoming email.

So, when I see an email like yours, full of unreadable (non-plain) text,
I look at the subject header.

Since "egcs-1.1.2 bug report" tells me basically nothing about whether
it's a Fortran (g77 or libg2c) bug, I ignore it.

Others might do the same, for their areas of expertise.

If you're going to submit bug reports in the various types of encoding
floating around on the 'net, I suggest you do at least one of the following
to ensure it gets paid attention to:

  -  Put a summary of the bug in plaintext at the top, e.g. "compiler
     crashed on C code".

  -  Put a one-line summary in the "Subject" header, e.g. "compiler crash
     on C code, egcs-1.1.2".

That being said, I'm personally much happier with some combination of
uuencode, gzip, bzip, and tar than with *anything* relating to MIME.
MIME decoding has worked about 2% of the times I've tried it.  The
other decoders work about 99% of the time.

        tq vm, (burley)