Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 17 Feb 2004 17:49:58 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: New snapshot available which *may* fix unzip long filenames problem Message-ID: <20040217224958.GA24244@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <20040217201833 DOT GA26980 AT redhat DOT com> <20040217205652 DOT GA314375 AT Worldnet> <20040217210628 DOT GB27861 AT redhat DOT com> <20040217224817 DOT GA91611 AT Worldnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040217224817.GA91611@Worldnet> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Tue, Feb 17, 2004 at 05:48:17PM -0500, Pierre A. Humblet wrote: >When you have a minute or two, could you think of an example where the >win32 name would have problems replacing the unix name in fhandler_*? fhandler_base::get_default_fmode is one place, I believe. I don't know if that functionality is actually used anywhere, though. I think all of the fhandler_proc stuff rely on it, but that's not really robust and could possibly be changed to get_win32 with some effort. chown_worker is one place where we *don't* need it, though. That could either be a path_conv or a fhandler, I think. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/