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:mime-version :content-type:content-transfer-encoding; q=dns; s=default; b=sqO 80yK4H5CERezOpKZgiFJfEDQeGnzfmTgxd26pIHEkQ0/OcnOSt2wAM8Ub5TET7PI lU2TF0EU62ywbPSxdbjpAbcQ74+ndRl87mjNwFUihM0OsVafdEu9Pb0UKfShV3WV xWP7GbViEdgHgKvjNtZ2QqrHOxV/3OB44LDkpEVo= 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:mime-version :content-type:content-transfer-encoding; s=default; bh=W5ElUQphS EYAYbUtlWoO3jHLyTQ=; b=L8LXE/H2cG5Kq5/mOoVBa1N5KHQ91J81p0RYjJnpP clOQEUtgX3TP+l8YRzHl9OU/tbfJYhHSksGUbsBFhqy2z1h9fLfqLt35xORWnNp6 5//GDahWwFW8utml0kaNhjPW0Ic8p4tQaQySwaUJinap35zXn9kLct4+RGlcpoIS fo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00,KAM_ASCII_DIVIDERS,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=communicate, Hx-languages-length:2801 X-HELO: mx02.jhcn.net From: Chevallier Yves To: "cygwin AT cygwin DOT com" Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) Date: Wed, 10 May 2017 11:30:53 +0000 Message-ID: <4fbaa9f1d22640179cff72187e7c70e8@de01ex22.GLOBAL.JHCN.NET> 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="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v4ABVIcG025310 I don't understand your points. See my reply below with the leading char $ This is the mail archive of the cygwin mailing list for the Cygwin project. ________________________________________ Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next] Other format: [Raw text] Re: cygpath compatiblity break (v2.1 -> v2.7) . From: Marco Atzeri . To: cygwin at cygwin dot com . Date: Wed, 10 May 2017 11:29:32 +0200 . Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) . Authentication-results: sourceware.org; auth=none . References: <2ebc717eaaf041d7b516e93a6123b938 AT de01ex22 DOT GLOBAL DOT JHCN DOT NET> <2b3a4976-09b2-cece-759d-0b2379ae3a4d AT gmail DOT com> ________________________________________ On 10/05/2017 11:12, Chevallier Yves wrote: 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. Bottom Post in this mailing list. Please. $ Is this a question? What do you please me for? Cygpath is part of the cygwin package. The source specific of "cygpath" is unchanged by ~ 6 months. The issue you see was likely a change inside the cygwin dll. $ Yes it is exactly what I was arguing because even if I change `cygpath.exe` for the oldest version, the issue is still the same About your internal validation, please note that the numbering scheme was changed with version 2.0 $ Which internal validation? Are you talking about `cygpath`? https://sourceware.org/ml/cygwin-announce/2015-04/msg00046.html I suggest you to consider 2.x version as the successor of 1.7.x. $ I am considering 2.7 instead of 2.1 What are you talking about 1.7? Regards Marco $ By the way I still don't know how to answer/reply a message from this mailing list. I have to do polling over https://www.cygwin.com/ml/cygwin/2017-05/ and copy/paste everything into a new e-mail. I doubt this is the correct way to communicate. Do you have a clue? -- 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 ________________________________________ . References: o Re: cygpath compatiblity break (v2.1 -> v2.7) . From: Chevallier Yves o Re: cygpath compatiblity break (v2.1 -> v2.7) . From: Marco Atzeri o RE: cygpath compatiblity break (v2.1 -> v2.7) . From: Chevallier Yves Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next] -- 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