Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 22 Oct 2001 20:33:56 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: 1.3.4 status? Message-ID: <20011022203356.C17641@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011022142729.A10309@redhat.com> User-Agent: Mutt/1.3.21i 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. cgf