From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: cygpath compatiblity break (v2.1 -> v2.7)
Date: Tue, 25 Apr 2017 16:46:00 -0000 [thread overview]
Message-ID: <vn4ufcp1liuesob71tg3ep64p2lreeu6fg@4ax.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A704BC07ED5@USA7109MB022.na.xerox.net>
> 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.207653@cygwin.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.
--
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 prev parent reply other threads:[~2017-04-25 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 9:17 Yves Chevallier
2017-04-25 10:10 ` Nellis, Kenneth (Conduent)
2017-04-25 16:46 ` Andrew Schulman [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2017-05-10 12:46 Chevallier Yves
[not found] ` <6e2d34a8-9af5-6288-280f-ed0fdb28d2a8@gmail.com>
[not found] ` <4fbf8b4194f6435298f17536ae08a35f@de01ex22.GLOBAL.JHCN.NET>
2017-05-10 13:11 ` Marco Atzeri
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-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=vn4ufcp1liuesob71tg3ep64p2lreeu6fg@4ax.com \
--to=schulman.andrew@epa.gov \
--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).