delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2001/10/27/12:46:15

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Sat, 27 Oct 2001 12:47:00 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: 1.3.4 status? [UPDATE]
Message-ID: <20011027124700.A12318@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <3BD4635D DOT 1060208 AT ece DOT gatech DOT edu> <20011022142729 DOT A10309 AT redhat DOT com> <20011022203356 DOT C17641 AT redhat DOT com>
Mime-Version: 1.0
In-Reply-To: <20011022203356.C17641@redhat.com>
User-Agent: Mutt/1.3.21i

On Mon, Oct 22, 2001 at 08:33:56PM -0400, Christopher Faylor wrote:
>On Mon, Oct 22, 2001 at 02:27:29PM -0400, Christopher Faylor wrote:
>>On Mon, Oct 22, 2001 at 02:20:13PM -0400, Charles Wilson wrote:
>>>Does anyone have a list of the outstanding issues that are preventing the 
>>>release of 1.3.4?  What are the showstoppers?
>>
>>Just five issues that I'm aware of:
>>
>>1) The supposed serial I/O bug.  (me)
>>
>>2) Corinna found a bug with ftpd today that needs to be fixed. (Corinna/me?)
>>
>>3) The HOMEDRIVE/HOMEPATH patch that will speed up cygwin and work around the
>>   gdb problem that people are having. (Corinna)
>>
>>4) Jonathan Kamens says that cygwin core dumps for him.  Havne't heard much
>>   about that. (jik)
>>
>>5) execvp (checked in soon) (me)
>
>Forgot one.  I'd like to fix the fseek bug that was recently mentioned in
>the cygwin list.
>
>Anyone want to track that down?  It should be relatively easy to fix, I think.

I believe that all of the above have been fixed except 1 and 2.

I'm willing to let cygwin out the door with 1 since I don't think I'm going
to be getting any high-quality feedback anytime soon.  It's been more than
a week and we're still in the "It works fine with I drop back to 1.3.2"
state.

Of course, if anyone has a serial connection to a windows system that would
allow them to check out this behavior, it would be appreciated.

cgf

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019