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:subject:references:to:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=rqi0KKLdKndnOs5v xP9Yjwnqt6UUqgeXdy06Mg+yd2doWv1PR+SI7A2nia31dR25D0ZsVoH8l9XvfXba oNbqWbNlSVb8GuMG2bmTkqIz+jyTDG3cbIZfIyLl2IPRLuF+FgPcHDoebDeIputJ HHHyrOpEBpuxrHz4Oe+iX7TNC/Y= 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:subject:references:to:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=m3GmIXlUNrGCptJr67JmIB sTEhQ=; b=Qg42/9LgTrDg9gD7qvMOEjUpkINllmcYCCNS08c8Dvav1+WD4zsfh8 kMdST54stTuIkxDTpQ6+vuCkY4uyVMpgNzfmQZ2/sXvSWamka5pVdhWpZiVOo7wW wjgjH/04Z8hhbPfHzOc3BNSEtC6MXCPO1+Ip58Nm/htKvDd2ro4KE= 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.9 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_1,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=retrieval, emails, yesterday X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.2 cv=F5wnTupN c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=nv5mQRr_bD-EAE1LQcUA:9 a=wvjUMX4N0GMQDAcP:21 a=7wGw5erPE7rhornL:21 a=QEXdDO2ut3YA:10 a=RznoDzx9x68A:10 a=_eVk2uPWGGoA:10 a=kBc5XBp1wVwA:10 a=aO5emRLkayEA:10 a=sRI3_1zDfAgwuvI8zelB:22 From: Brian Inglis Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) 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> To: cygwin AT cygwin DOT com Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Message-ID: <5dca8524-044a-3549-90a5-6dca909b0967@SystematicSw.ab.ca> Date: Wed, 26 Apr 2017 10:37:34 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <3094b7cc-7745-1160-e77e-0ef8b90bd150@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfFziP0/voQeWaywgVrinC2Hg2sEeviV3qwYYDIsilD2twB2BrTLIHFLKwNiExI1SIMBGutkwi8zJOPnB8BkudwWYaUfsT7Cne1G9m0+uouYrxEfHAtsi xdaHG8ltI6gj2lIJqseYZNB0yPFY/kMo0FsDKSETc0pzrPsbgOGYqT/YILUHo5wbbo/Xx0hH/UjCsg== X-IsSubscribed: yes 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