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:from:to:subject:date:message-id:references
	:in-reply-to:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=fDdwX9y5VTnKcl9U
	A9WzwxCGCooB6XyKvP2mN9SMfnt5fbvPsSOCKTJ6C23ccPQPdG/1BNlZ6U4btDwm
	gkuttAEfJ1KsstoSAIjkWixRBRO0dYyZ7ANpTdX2FETnksw/jXLAHW/h7VTl/h6W
	VFoepyVlYdDKus80+pU/d32h4MA=
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:from:to:subject:date:message-id:references
	:in-reply-to:mime-version:content-type
	:content-transfer-encoding; s=default; bh=t8Ubzfw6GaQdOxosVTMcKz
	QqyEY=; b=AgHCyrt63I8cmwWGigZ/jCGL2GihPkakHKyRvdqrQ+WITBojez+xNp
	OK9dbRKnnjjQqlCvsOrnq+jMVi3Ge8h5xOMxajV8/flbW82kA5z0I8Z18e1x2vdt
	73TRxX/LAlJJgxvNPOuc4Sq4ydkOG+d19MRNsXHJ9PPKmU+V4a+c8=
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=-5.7 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=2.8, H*f:sk:2ebc717, dear, Dear
X-HELO: mx02.jhcn.net
From: Chevallier Yves <YChevallier AT etel DOT ch>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: cygpath compatiblity break (v2.1 -> v2.7)
Date: Wed, 10 May 2017 09:12:27 +0000
Message-ID: <edde67b3a1724bb484eb82cd48dcee67@de01ex22.GLOBAL.JHCN.NET>
References: <2ebc717eaaf041d7b516e93a6123b938 AT de01ex22 DOT GLOBAL DOT JHCN DOT NET> <2b3a4976-09b2-cece-759d-0b2379ae3a4d AT gmail DOT com>
In-Reply-To: <2b3a4976-09b2-cece-759d-0b2379ae3a4d@gmail.com>
x-ms-exchange-transport-fromentityheader: Hosted
x-gfi-smtp-submission: 1
x-gfi-smtp-hellodomain: de01ex22.GLOBAL.JHCN.NET
x-gfi-smtp-remoteip: 10.1.76.197
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v4A9Cka4017188

Unfortunately I haven't tried 2.8 because we've already validated 2.7 internally and I would need at least 3 months to access to 2.8. 

That said I searched for a release note with information about cygpath, but I haven't find any. 

-----Original Message-----
From: Marco Atzeri [mailto:marco DOT atzeri AT gmail DOT com] 
Sent: mercredi 10 mai 2017 09:14
To: cygwin AT cygwin DOT com
Cc: Chevallier Yves <YChevallier AT etel DOT ch>
Subject: Re: cygpath compatiblity break (v2.1 -> v2.7)

On 10/05/2017 08:00, Chevallier Yves wrote:
> Dear All,
>
> I tried to understand how the mailing list work, but I cannot find any thread number or message number from the following.
>
> Moreover we haven't discussed my issue with `cygpath` which is a serious compatibility break in my toolchain. Changing the executable doesn't change anything because I think `cygpath` is somehow linked to a Cygwin dll which have the bug.
>
> So two questions in this thread:
>
> 1. How can I participate to the thread and use this mailing list properly?
> 2. What workaround can I use with my Cypath issue?
>
> Regards,
> Yves


Have you tried 2.8 ?

https://cygwin.com/ml/cygwin/2017-04/msg00156.html





--
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