Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <000d01c11529$0a46a950$47a23209@fishkill.ibm.com> From: "John Fortin" To: References: <034601c11505$0a368710$6d07a8c0 AT miro> <001d01c1151e$aa4b7a80$47a23209 AT fishkill DOT ibm DOT com> <3B5EE9C1 DOT 5060102 AT ece DOT gatech DOT edu> Subject: Re: is cygwin lame??? Date: Wed, 25 Jul 2001 12:44:14 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 > John, > > Chill, dude. Sure, Michael's subject line is less-than-inspiring, but > the message content was thorough, showed that he has researched his > performance problem, and pinpointed the cause. I'll trade > that for a "nice" subject line+clueless message body ANY day. Sorry, things like that just press my buttons sometimes... > > If he'd also been able to include a patch to fix the problem, I'd > probably wet my pants. :-) > > --Chuck > > BTW, why'd did you BCC: the cygwin list? Blind copying makes it hard to > keep message threads/replies on-list; requires manual intervention of > prospective reply-ees. Hmmm, I have no idea. When I sent it, the mail-list was in the TO: field.... John -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/