public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'wibbly little fishies'" <cygwin-talk@cygwin.com>
Subject: RE: Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18]
Date: Mon, 04 Jul 2005 18:44:00 -0000	[thread overview]
Message-ID: <SERRANOgIxRhrLjANJQ00000383@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <20050704183016.GA20441@trixie.casa.cgf.cx>

----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...
> 
> cgf


  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!

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2005-07-04 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 18:18 Dave Korn
2005-07-04 18:30 ` Christopher Faylor
2005-07-04 18:44   ` Dave Korn [this message]
2005-07-04 23:11     ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SERRANOgIxRhrLjANJQ00000383@SERRANO.CAM.ARTIMI.COM \
    --to=dave.korn@artimi.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).