X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 11 Jul 2006 12:09:05 -0400 From: "Lev Bishop" To: cygwin AT cygwin DOT com Subject: Re: Cgywin filename with 255 character In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Disposition: inline References: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k6BG9EVi014695 On 7/11/06, Jörg Schaible wrote: > Is there any pointer at MS, where this is described exaclty? I was only able to find some entries in the knowledge base that describe applications that are affected by this limit, but nowhere an explanation under what circumstances a process/application is hit by this limit. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp -- 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/