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=Mdz KeDVOjG5tEWdMpOJ/s+ALKeV9e+34iASz6sDcWe+5LCT+pl8146RdHAO/ccDM+dm xZwS0OUKXSOUR3ZkyXo3XRExzE1ESBl27A6iECg+FCvByJuS2QZ2kWRG4p9DVlKm Vepro5z9/bZm8Xchs1bE8UMQpRxRtRW16MZCNh6o= 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=faYF2mpJA a/IKLFCnznsXGOhWyU=; b=WDvjtpbSRfSvPa7QcEuzFYfBs2DiZ1w+fabQrx2uD aF5KQeFbQ4fPRay+PziFHaiL17L8lj3hI+uJSFHBumsC5T7kN2jZkL6tJ7hIdgCu rzdf72bzw5nMLU2jbbL1uv5AV51hPKVE9zosTG63J9g2V8S9/6vXmWrMvstaVgCR 6Q= 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=-5.4 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_1,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=subscribed, HX-Envelope-From:prvs, acknowledgement, Replyto 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 06:00:16 +0000 Message-ID: <2ebc717eaaf041d7b516e93a6123b938@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="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v4A6llkc008647 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 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: <0D835E9B9CD07F40A48423F80D3B5A704BC07ED5 AT USA7109MB022 DOT na DOT xerox DOT net> <7ddd6386-4463-ec7e-14b0-dc1b719c9607 AT SystematicSw DOT ab DOT ca> <36feeb13-b77d-1c2a-d31a-e1e6241e43bb AT SystematicSw DOT ab DOT ca> <3094b7cc-7745-1160-e77e-0ef8b90bd150 AT gmail DOT com> 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 cygwin-get DOT 207653 AT cygwin DOT com. 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 -help AT cygwin DOT com e.g. mailto:cygwin-help AT cygwin DOT com. >> [last line scrambled by email address obscurer] >> email to -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: To get an index with subject and author for messages 123-456 , mail: 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: " 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