From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: "'The Cygwin-Talk Malingering List'" <cygwin-talk@cygwin.com>
Subject: RE: The 20060324/20060326 snapshots hang on testcase
Date: Wed, 29 Mar 2006 00:29:00 -0000 [thread overview]
Message-ID: <003201c652c7$d1f260d0$020aa8c0@DFW5RB41> (raw)
In-Reply-To: <04f001c65250$80c87540$a501a8c0@CAM.ARTIMI.COM>
> From: Dave Korn
> Sent: Tuesday, March 28, 2006 4:15 AM
> To: Thread TITTTL'd!
> Subject: RE: The 20060324/20060326 snapshots hang on testcase
>
> On 28 March 2006 06:43, Gary R. Van Sickle wrote:
>
> Oi Gary! This thread needs TITTTL'ing!
>
But think of the chickens Dave! Won't somebody think of the chickens?!?!?
> >> From: Dave Korn
> >> Sent: Monday, March 27, 2006 5:00 AM
> >> To: cygwin@cygwin
> >> Subject: RE: The 20060324/20060326 snapshots hang on testcase
> >>
> >> On 27 March 2006 04:04, Volker Quetschke wrote:
> >>
> >>> The newest 20060324/20060326 snapshots started to hang on the
> >>> following testcase. Note, I only tried the following versions:
> >>>
> >>> release 1.5.19 no hang
> >>> snapshot 20060306 no hang
> >>> snapshot 20060324 hangs
> >>> snapshot 20060326 hangs
> >>
> >> CVS 20060317: no hang.
> >>
> >> [ Just to help refine the search a bit. ]
> >>
> >
> > Ahem, without resolution to the minute that's going to help
> how again?
> >
>
> Why would you need resolution to the minute unless someone
> was making changes in /src/winsup equally frequently? I had
> a data point that was handily in between the 6th and the
> 24th, in fact it was more or less a binary chop of the range
> that had still to be reduced and halved it!
>
Yeah, to you and me maybe that makes total sense. But to somebody who can
track down and fix a bug he and/or she didn't even know existed PLUS post
two emails about it in less than nineteen minutes, and still thinks that's
too slow, I SUBMIT TO YOU THAT IT IS NOT SIR! Your binary choppery would
have only reduced that to 9.5 minutes - STILL NOT FAST ENOUGH I SAY! Had
you had at least a shred of human decency and had narrowed this chasm of
time down to the minute wherein the issue presented itself, you would have
reduced this post/duplicate/find/fix/post cycle time to:
8 days * 86400 secs/day... Carry the five... One-over...
TWENTY SEVEN MICROSECONDS!
<Conan-O'Brien-Zell-Miller-On-The-Drop-Down-TV-Voice>
How DARE you sir!
</Conan-ah-whatever-you-know-the-drill>
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>
--
Gary R. Van Sickle
prev parent reply other threads:[~2006-03-29 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000a01c6522a$7c016c90$020aa8c0@DFW5RB41>
2006-03-28 10:15 ` Dave Korn
2006-03-29 0:29 ` Gary R. Van Sickle [this message]
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='003201c652c7$d1f260d0$020aa8c0@DFW5RB41' \
--to=g.r.vansickle@worldnet.att.net \
--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).