This is the mail archive of the cygwin-talk mailing list for the cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: html email (was Re: cygserver blocking on semctl(SETVAL) call)


Christopher Faylor wrote:
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.

Because, as you pointed out, it is a stupid discussion? My own instinct is to move anything that isn't Cygwin to -talk. This is about the list, not Cygwin itself. But it was a border area, so if I have anything purposeful to say I'll move it back.


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.

No argument here. :-)


--
Matthew
We are Microsoft. You will be assimilated. Resistance is futile. --Badtech


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]