This is the mail archive of the
mailing list for the cygwin project.
html email (was Re: cygserver blocking on semctl(SETVAL) call)
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Mon, 28 Aug 2006 15:25:39 -0400
- Subject: html email (was Re: cygserver blocking on semctl(SETVAL) call)
- References: <CEFD7032-DD32-4F1E-8D2F-C706BE73F470@andrew.cmu.edu> <44EF5431.email@example.com> <C33FC55B-5CDC-4FB3-942E-43F7DB5819AC@andrew.cmu.edu> <44F33FDF.firstname.lastname@example.org>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On Mon, Aug 28, 2006 at 02:11:27PM -0500, mwoehlke wrote:
>Ethan Tira-Thompson wrote:
>>PS First attempt of this email got kicked back because it had a
>>text/html mime type alongside the text/plain.
>You mean we actually do that? Sweet!
Yes, and as you surmised, it is a fairly good intelligence filter.
Btw, why move this topic to the cygwin-talk list? As much as I think
it's a stupid discussion, it is on-topic for the cygwin list.
>>Wouldn't it be nice to have syntax-highlighted code samples?
>If you plan to highlight your example code (and by what standard?), you
>have too much time on your hands.
>For the record, GRC's newsgroup also rejects HTML messages (as well as
>anything over 20kb), so Cygwin isn't alone here.
There are a lot of mailing lists at sourceware.org and gcc.gnu.org with
the same policy.
But, IMO, the technique of "I would like you to help me but, before I
do, let me tell you that the method you've chosen to allow me to do that
is really not to my liking" still seems like a pretty bad way of asking
for help if you are expecting results.