From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7054 invoked by alias); 4 Jul 2005 23:11:39 -0000 Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Cygwin-Talk Malingering List Received: (qmail 7038 invoked by uid 22791); 4 Jul 2005 23:11:36 -0000 Received: from c-24-61-23-223.hsd1.ma.comcast.net (HELO cgf.cx) (24.61.23.223) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 04 Jul 2005 23:11:36 +0000 Received: by cgf.cx (Postfix, from userid 201) id EFB7C13C0D2; Mon, 4 Jul 2005 19:11:27 -0400 (EDT) Date: Mon, 04 Jul 2005 23:11:00 -0000 From: Christopher Faylor To: The Cygwin-Talk Malingering List Subject: Re: Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18] Message-ID: <20050704231127.GC20441@trixie.casa.cgf.cx> Reply-To: cygwin-talk@cygwin.com Mail-Followup-To: The Cygwin-Talk Malingering List References: <20050704183016.GA20441@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-q3/txt/msg00005.txt.bz2 On Mon, Jul 04, 2005 at 07:43:57PM +0100, Dave Korn wrote: >----Original Message---- >>From: Christopher Faylor >>Sent: 04 July 2005 19:30 > >> On Mon, Jul 04, 2005 at 07:17:59PM +0100, Dave Korn wrote: >>>> From: Christopher Faylor >>>> Sent: 04 July 2005 19:11 >>> >>>> The division of labor should be like this: >>>> >>>> The reporter: .. >>> >>> ... will send the following message to the mailing list: >>> >>> " Cygwin, you sucK! IT broKen, you fix it now!" >> >>OTOH, by sending strace output, you can bask in the knowledge that >>you've done "something technical" and, so, therefore, are actually >>helping in a constructive way rather than just complaining. >> >>You'll be even more helpful if you inspect the output and trim away all >>of the stuff you know is unneeded even though the whole reason you're >>sending the strace output is that you don't know cygwin well enough to >>fix the problem and so, therefore, your attempt to trim the output is >>likely to trim away useful bits... > >Even better, come up with a simple test case, and post it to the list, >but then, because it doesn't quite show the problem like you expected >it to, 'adjust' the output from your shell as you cut'n'paste it into >the email, to make it more 'correct'. I love that one! Yeah, that was a classic. You know this suggests a way that I could always win every argument. I have edit rights to the cygwin archive. Hmm... cgf