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 Subject: Re: is cygwin lame??? From: Robert Collins To: Charles Wilson Cc: John Fortin , cygwin AT cygwin DOT com In-Reply-To: <3B5EED45.2030109@ece.gatech.edu> References: <034601c11505$0a368710$6d07a8c0 AT miro> <001d01c1151e$aa4b7a80$47a23209 AT fishkill DOT ibm DOT com> <3B5EED45 DOT 2030109 AT ece DOT gatech DOT edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11 (Beta Release) Date: 26 Jul 2001 09:39:45 +1000 Message-Id: <996104386.18052.16.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 25 Jul 2001 23:26:04.0265 (UTC) FILETIME=[2C51BD90:01C11561] On 25 Jul 2001 12:01:09 -0400, Charles Wilson wrote: > > 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. > > 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. (and it's been so long since I actually > *initiated* a thread, I typed the cgywin mailing address in wrong the > first time...) > Try a different mailer :}. Evolution kept the messages threaded without trouble. Rob -- 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/