Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18]

Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18]

[Dave Korn]

----Original Message----
>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!"

> In a similar "why bother?" vein, it is generally not useful to provide
> "me too" observations unless ..

 ... you are from AOL and recognize that YA superfluous "me too" is probably
as much of a contribution as you'll ever be able to make to the overall
wealth of human knowledge and culture ...


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

Re: Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18]

[Christopher Faylor]

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

RE: Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18]

[Dave Korn]

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

Re: Bug report [was FW: Freeze in perl script after cygwin upgrade 1.5.17 -> 1.5.18]

[Christopher Faylor]

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