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 From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca> To: 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: <caa65n5wf9ri_igb1oscx9deg6rttytvhyukfq012dpqmbdz...@mail.gmail.com> <0d835e9b9cd07f40a48423f80d3b5a704bc07...@usa7109mb022.na.xerox.net> <[email protected]> <[email protected]> <[email protected]> <[email protected]> Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca 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 >>>>>> https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html? >>>>> Send a plain-text e-mail to [email protected]. No >>>>> need to add a subject or body. It will send you the message, >>>>> and you can reply to that. >>>> Whoa. This should be documented somewhere. >>>> Looks like the 207653 comes from the Return-Path header when >>>> you view the raw message content. >>> It's documented in all subscription confirmation and acknowledgement >>> emails from the mailing list manager, unless you subscribed before >>> ezmlm was used, and you can get it by sending a blank plain text >>> email to <list>[email protected] e.g. mailto:[email protected]. >> [last line scrambled by email address obscurer] >> email to <list>-help at cygwin dot com e.g. cygwin-help at cygwin dot com > 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. Other lists' help is more informative - single message retrieval based on the ml msg# is implied, but the source of that number is not obvious: "To get messages 123 through 145 (a maximum of 100 per request), mail: <[email protected]> To get an index with subject and author for messages 123-456 , mail: <[email protected]> They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: <[email protected]>" should be added to the cygwin ml help, as should the source of the msg# as being the number in the raw message Return-path: header, and -help should be a command, and added to the ml help. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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 -- 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
