Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 28 Feb 2003 12:42:45 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Releasing new sh-utils now with access() change? Message-ID: <20030228174245.GE10456@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20030228170058 DOT GA9681 AT redhat DOT com> <3E5F9E9C DOT 6A00AA6E AT ieee DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E5F9E9C.6A00AA6E@ieee.org> User-Agent: Mutt/1.5.1i On Fri, Feb 28, 2003 at 12:38:36PM -0500, Pierre A. Humblet wrote: >Christopher Faylor wrote: >>There is no reason for me to hold off on releasing a new sh-utils, with >>the eaccess -> access change now, right? /bin/test won't work any >>worse than it does already with this change, right? > >Chris, > >I would not release a new /bin/test until 1.3.21 is out. With 1.3.20 >the behavior will be different, sometimes better, sometimes worse. In >particular the current /bin/test always produces correct results on >files created by Cygwin, while sh (and the new /bin/test ) currently >don't. Ok. No problem. Releasing it now was just one less thing for me to remember when I eventually produce 1.3.21 but it's no big deal to wait. cgf