RE: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-10 Thread Nellis, Kenneth (Conduent)
From: Chevallier Yves > ... > So two questions in this thread: > 1. How can I participate to the thread and use this mailing list properly? > ... > From: Brian Inglis > ... > Looks like the 207653 comes from the Return-Path header when > you view the raw message content. The answer was

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-10 Thread Marco Atzeri
On 10/05/2017 14:35, Chevallier Yves wrote: I don't want to suscribe to it, I just want to be able to post and reply not more. Or you subscribe or you use a NNTP gateway. https://cygwin.com/news.html There are no other way. There is no issue tracker for Cygwin. This is not very convenien

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-10 Thread Chevallier Yves
[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: sourcewar

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-10 Thread Marco Atzeri
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 th

RE: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-10 Thread Chevallier Yves
m: Marco Atzeri [mailto:marco.atz...@gmail.com] Sent: mercredi 10 mai 2017 09:14 To: cygwin@cygwin.com Cc: Chevallier Yves 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 f

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-10 Thread Marco Atzeri
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. Changi

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-05-09 Thread Chevallier Yves
cygwin at cygwin dot com Date: Wed, 26 Apr 2017 10:37:34 -0600 Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) Authentication-results: sourceware.org; auth=none References: <0d835e9b9cd07f40a48423f80d3b5a704bc07...@usa7109mb022.na.xerox.net> <7ddd6386-4463-ec7e-14b0-dc1b719c9

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-26 Thread Brian Inglis
On 2017-04-26 09:20, cyg Simple wrote: > On 4/25/2017 9:51 PM, Brian Inglis wrote: >> On 2017-04-25 19:12, Brian Inglis wrote: >>> On 2017-04-25 03:16, Andrew Schulman wrote: > From: Yves Chevallier >> How can I use this mailing list to answer a mail that I >> only find from this link

RE: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-26 Thread Nellis, Kenneth (Conduent)
From: cyg Simple > I was going to state the same yesterday but I gave it a try first. The > resulting mail doesn't explain the use of cygwin-get.MSGID that I saw. > It mostly refers to the FAQ on cygwin.com. Well, there is the following. Not saying it is easy to find. https://untroubled.org/ezm

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-26 Thread cyg Simple
On 4/25/2017 9:51 PM, Brian Inglis wrote: > On 2017-04-25 19:12, Brian Inglis wrote: >> On 2017-04-25 03:16, Andrew Schulman wrote: From: Yves Chevallier > How can I use this mailing list to answer a mail that I only > find from this link > https://www.cygwin.com/ml/cygwin/2017-04

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-25 Thread Brian Inglis
On 2017-04-25 19:12, Brian Inglis wrote: > On 2017-04-25 03:16, Andrew Schulman wrote: >>> From: Yves Chevallier How can I use this mailing list to answer a mail that I only find from this link https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html? >>> Send a plain-text e-mail to c

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-25 Thread Brian Inglis
On 2017-04-25 03:16, Andrew Schulman wrote: >> From: Yves Chevallier >>> How can I use this mailing list to answer a mail that I only >>> find from this link >>> https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html? >> Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need >> to add a

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-25 Thread Andrew Schulman
> From: Yves Chevallier > > ... > > How can I use this mailing list to answer a mail that I only find from > > this [link](https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html)? > > ... > > Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need to add > a subject or body. It will sen

RE: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-24 Thread Nellis, Kenneth (Conduent)
From: Yves Chevallier > ... > How can I use this mailing list to answer a mail that I only find from > this [link](https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html)? > ... Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need to add a subject or body. It will send you the messag

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-24 Thread Yves Chevallier
Well, I don't have the same behavior and I have the latest version of `cygpath.exe` according to my setup: $ cd / $ mkdir foo $ touch foo.exe $ cygpath -w foo foo $ cd foo $ touch foo.exe $ cygpath -w foo foo.exe $ cygpath --version cygpath (cygwin) 2.8.0 Path Conversion Utility Copyright (

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread Marco Atzeri
On 13/04/2017 14:34, Chevallier Yves wrote: I get a very different behaviour with `cygpath` after I upgrade my version of Cygwin. Why? and how can I fix it? With Cygwin 2.7: ``` $ uname -a CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 2017-02-12 13:13 i686 Cygwin $ cygpath --version cygpath (cygwin)

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread David Macek
On 13. 4. 2017 16:24, David Macek wrote: > On 13. 4. 2017 14:34, Chevallier Yves wrote: >> I get a very different behaviour with `cygpath` after I upgrade my version >> of Cygwin. Why? and how can I fix it? >> >> With Cygwin 2.7: >> >> ``` >> $ uname -a >> CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 20

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread David Macek
On 13. 4. 2017 14:34, Chevallier Yves wrote: > I get a very different behaviour with `cygpath` after I upgrade my version of > Cygwin. Why? and how can I fix it? > > With Cygwin 2.7: > > ``` > $ uname -a > CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 2017-02-12 13:13 i686 Cygwin > $ cygpath --version

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread cyg Simple
On 4/13/2017 10:02 AM, Eric Blake wrote: > On 04/13/2017 08:59 AM, cyg Simple wrote: > > [an unreadable encrypted message] > > You may want to fix your email settings; encrypted messages should > generally not be used when sending to a mailing list. > Sorry, Enigmail settings must have changed

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread Eric Blake
On 04/13/2017 08:59 AM, cyg Simple wrote: [an unreadable encrypted message] You may want to fix your email settings; encrypted messages should generally not be used when sending to a mailing list. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization:

Re: cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread cyg Simple
binD9fTojUuRq.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message

cygpath compatiblity break (v2.1 -> v2.7)

2017-04-13 Thread Chevallier Yves
I get a very different behaviour with `cygpath` after I upgrade my version of Cygwin. Why? and how can I fix it? With Cygwin 2.7: ``` $ uname -a CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 2017-02-12 13:13 i686 Cygwin $ cygpath --version cygpath (cygwin) 2.7.0 $ cd / $ touch foo.exe $ cygpath -m fo