From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.1
Date: Mon, 25 Jan 2016 09:29:00 -0000 [thread overview]
Message-ID: <56A59132.600@cornell.edu> (raw)
In-Reply-To: <20160124225744.GC27138@calimero.vinschen.de>
On 1/24/2016 5:57 PM, Corinna Vinschen wrote:
> Does it fail to create ACLs? Do the created ACLs make sense? If you
> have a file created with Cygwin >= 2.4.0 and change the file content
> with Emacs, does the ACL change or stay the same? Stuff like that.
I've tested everything I can think of (including emacs's functions for
viewing and changing ACLs), and it all seems to work fine. I can
provide more details if you want.
Ken
--
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:[~2016-01-25 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 19:30 Corinna Vinschen
2016-01-24 22:32 ` Ken Brown
2016-01-25 2:55 ` Corinna Vinschen
2016-01-25 9:29 ` Ken Brown [this message]
2016-01-25 14:58 ` Corinna Vinschen
2016-01-25 9:30 ` Thorsten Kampe
2016-01-25 11:02 ` 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=56A59132.600@cornell.edu \
--to=kbrown@cornell.edu \
--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).