From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18467 invoked by alias); 11 Dec 2011 20:30:31 -0000 Received: (qmail 18459 invoked by uid 22791); 11 Dec 2011 20:30:31 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ee0-f43.google.com (HELO mail-ee0-f43.google.com) (74.125.83.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 11 Dec 2011 20:30:18 +0000 Received: by eekd49 with SMTP id d49so2776250eek.2 for ; Sun, 11 Dec 2011 12:30:16 -0800 (PST) Received: by 10.14.8.9 with SMTP id 9mr2115535eeq.205.1323635416835; Sun, 11 Dec 2011 12:30:16 -0800 (PST) Received: from [192.168.2.195] (93-33-97-11.ip44.fastwebnet.it. [93.33.97.11]) by mx.google.com with ESMTPS id z54sm65662492eeh.5.2011.12.11.12.30.15 (version=SSLv3 cipher=OTHER); Sun, 11 Dec 2011 12:30:15 -0800 (PST) Message-ID: <4EE512D7.3080908@gmail.com> Date: Sun, 11 Dec 2011 20:30:00 -0000 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin-talk@cygwin.com Subject: Fwd: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10 References: <20111211192516.GA22458@ednor.casa.cgf.cx> In-Reply-To: <20111211192516.GA22458@ednor.casa.cgf.cx> X-Forwarded-Message-Id: <20111211192516.GA22458@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2011-q4/txt/msg00043.txt.bz2 On Sun, Dec 11, 2011 at 08:07:12AM +0100, marco atzeri wrote: >On 12/11/2011 7:34 AM, Christopher Faylor wrote: > >>> The issue is still present from 20111129 to current CVS (fith select). >>> Any clue ? >> >> The hanging problem should be fixed in recent snapshots. > >it was fixed on yesterday CVS Actually, it should have been fixed a couple of days ago. cgf probably, but I was out for few days Cheers Marco