public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "Thread TITTTL'd!" <cygwin-talk@cygwin.com>
Subject: RE: The 20060324/20060326 snapshots hang on testcase
Date: Tue, 28 Mar 2006 10:15:00 -0000	[thread overview]
Message-ID: <04f001c65250$80c87540$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <000a01c6522a$7c016c90$020aa8c0@DFW5RB41>

On 28 March 2006 06:43, Gary R. Van Sickle wrote:

  Oi Gary!  This thread needs TITTTL'ing!

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


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

       reply	other threads:[~2006-03-28 10:15 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 [this message]
2006-03-29  0:29   ` Gary R. Van Sickle

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='04f001c65250$80c87540$a501a8c0@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).