X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=CG/H8Z9zpvxyHWAYuthccvq9UslmI+VmE3ZLwe9BEZtMNIRFxZyh3
	j6rs/rntHcNxB+s0i96ukHrvnEdIhRxNE+CqopG4T2IjXpoN2E9qbGMC2TinCoC2
	U8FnmEX9LHnjU7wOPDyPN+HTCSDHLmqcjjNo1ShagzlPjKxUwzo1YE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=bweKDNReVY5sNE4jCakr1lFvqdk=; b=VVZLvxR4AOMYbKXkb3eVtjaUU13e
	IXXf7D/Y83sZtweL5URd+qn4nyTt2ks2peJ10gCotWN96AoRoYw4sbCCQFzqyLo4
	nFtXCLnneWGgfsvPaah/Pa3EfKZYUEOn4go90MKZQLuVcaMbpyMJ7TNJDUjSNQpB
	swwOKl5p0WVCU+o=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00,LIKELY_SPAM_SUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1823NWY6Z3E0DaI/qtWC8q1
Date: Tue, 10 Dec 2013 11:29:15 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cant access to files more than 128 utf-8 symbol long names
Message-ID: <20131210162915.GB751@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <52A6BFA4 DOT 9010101 AT spektr-rfs DOT ru> <20131210102755 DOT GQ2527 AT calimero DOT vinschen DOT de> <52A729AC DOT 1020906 AT gmail DOT com> <20131210153259 DOT GT2527 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131210153259.GT2527@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Dec 10, 2013 at 04:32:59PM +0100, Corinna Vinschen wrote:
>On Dec 10 16:48, Noel Grandin wrote:
>>On 2013-12-10 12:27, Corinna Vinschen wrote:
>>>Sorry if that is frustrating in your current situation, but this isn't
>>>something we can just change at a whim and go ahead.  It would break
>>>compatibility with all existing Cygwin executables.
>>
>>Maybe this is something that could be fixed only in the 64-bit version
>>of Cygwin?
>
>Did you really read my mail?  There is no fix.  You can handle this
>wrongly one way or the other.  If in doubt, I prefer the POSIXly
>correct way.

Also, even if it was something that could be "fixed", since the 64-bit
version of Cygwin has been out for some time now, breaking backwards
compatibility would still be bad.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple