delorie.com/archives/browse.cgi | search |
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: | Mon, 6 Aug 2001 21:32:35 -0400 |
From: | Christopher Faylor <cgf AT redhat DOT com> |
To: | cygwin-developers AT cygwin DOT com |
Subject: | outstanding issues blocking new release? |
Message-ID: | <20010806213235.A24499@redhat.com> |
Reply-To: | cygwin-developers AT cygwin DOT com |
Mail-Followup-To: | cygwin-developers AT cygwin DOT com |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.3.11i |
I can only think of three issues with cygwin that may need addressing. 1) The close_all_files problem that Egor found with exec'ed processes. 2) The problem with select() not detecting eof on pipes (Corinna really wants me to fix this). 3) The ntsec inheritance stuff. Is there anything more? Of the three, I think the most important one is probably 1). The other two are potentially enough too major to consider if I want to make a new release. What I'd like to do is fix 1) and then ask people on the cygwin mailing list to try out snapshots. If the snapshot seems to work ok, I'll make a 1.3.3 release. I'm still a tiny bit concerned about Windows 9x/Me but maybe people will test this if I ask about it in the cygwin mailing list... cgf
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |