From: Chevallier Yves <YChevallier@etel.ch>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: cygpath compatiblity break (v2.1 -> v2.7)
Date: Wed, 10 May 2017 12:46:00 -0000 [thread overview]
Message-ID: <4fbaa9f1d22640179cff72187e7c70e8@de01ex22.GLOBAL.JHCN.NET> (raw)
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 <marco dot atzeri at gmail dot com>
. 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@de01ex22.GLOBAL.JHCN.NET> <2b3a4976-09b2-cece-759d-0b2379ae3a4d@gmail.com> <edde67b3a1724bb484eb82cd48dcee67@de01ex22.GLOBAL.JHCN.NET>
________________________________________
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
next reply other threads:[~2017-05-10 11:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 12:46 Chevallier Yves [this message]
[not found] ` <6e2d34a8-9af5-6288-280f-ed0fdb28d2a8@gmail.com>
[not found] ` <4fbf8b4194f6435298f17536ae08a35f@de01ex22.GLOBAL.JHCN.NET>
2017-05-10 13:11 ` Marco Atzeri
-- strict thread matches above, loose matches on Subject: below --
2017-05-10 7:13 Chevallier Yves
2017-05-10 9:12 ` Marco Atzeri
2017-05-10 9:29 ` Chevallier Yves
2017-05-10 9:30 ` Marco Atzeri
2017-05-10 14:12 ` Nellis, Kenneth (Conduent)
2017-04-25 9:17 Yves Chevallier
2017-04-25 10:10 ` Nellis, Kenneth (Conduent)
2017-04-25 16:46 ` Andrew Schulman
2017-04-26 15:45 ` Brian Inglis
2017-04-26 19:06 ` Brian Inglis
2017-04-27 8:46 ` cyg Simple
2017-04-27 9:22 ` Nellis, Kenneth (Conduent)
2017-04-27 12:29 ` Brian Inglis
2017-04-13 13:29 Chevallier Yves
2017-04-13 14:12 ` cyg Simple
2017-04-13 14:14 ` Eric Blake
2017-04-13 14:29 ` cyg Simple
2017-04-13 17:42 ` David Macek
2017-04-13 18:01 ` David Macek
2017-04-13 18:34 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4fbaa9f1d22640179cff72187e7c70e8@de01ex22.GLOBAL.JHCN.NET \
--to=ychevallier@etel.ch \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).