From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1
Date: Sat, 11 Apr 2015 16:47:00 -0000 [thread overview]
Message-ID: <4edf7e559b745a1f7bec099e296263d9.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20150411145223.GK7343@calimero.vinschen.de>
>> Reference: https://cygwin.com/ml/cygwin/2015-04/msg00201.html
>> - [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1
>
> I really appreciate bug reports, but, please, try to keep the threading
> intact. Please reply to mails rather than creating new threads which
> have no connection to the original threads. Or if so, at least set the
> "In-Reply-To:" Header field correctly.
:-) ... I understand ... my problem is, that I am usually NOT subscribed
to the (any) list, and that I process all my e-mail using webmail, and as
far as I aware of, it does not provide the "In-Reply-To" feature.
As a result of that, my "first" e-mail will be "out-of-line". Sigh.
[snip]
> Btw., the output from SetACL isn't that helpful, because it doesn't
> add information to what icacls already delivers. What I'd be more
> interested in is the output of our own getfacl in conjunction with
> icacls. It allows me to see the POSIX ACL the internal ACL reading
> routine created from the Windows ACL.
:-) Will do!
Regards,
Henri
--
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:[~2015-04-11 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 13:25 Correct? (Cygwin 2.0) Houder
2015-04-11 14:52 ` [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1 Corinna Vinschen
2015-04-11 16:47 ` Houder [this message]
2015-04-11 17:28 ` Achim Gratz
2015-04-12 7:54 ` Houder
-- strict thread matches above, loose matches on Subject: below --
2015-04-11 10:40 Corinna Vinschen
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=4edf7e559b745a1f7bec099e296263d9.squirrel@webmail.xs4all.nl \
--to=houder@xs4all.nl \
--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).