From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.18
Date: Fri, 15 Jan 2016 17:27:00 -0000 [thread overview]
Message-ID: <20160115143433.GB12431@calimero.vinschen.de> (raw)
In-Reply-To: <20160114091742.GA2747@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Jan 14 10:17, Corinna Vinschen wrote:
> On Jan 13 12:48, random user wrote:
> > >> It's a bit late now to change how Cygwin constructs and evaluates ACLs.
> >
> > Sorry, with the holidays and other issues it wasn't possible for me to
> > look at the test drops earlier.
>
> We're testing this Cygwin change for four(!) months now. I release
> the first one on Sep 2nd. It's a bit late now just to support some
> border case within 48 hours before the release. Also consider that
> NFSv4 uses yet another way to create POSIX-like ACLs which apparently
> doesn't match the NTFS-3G layout either. It's not so much the layout
> of the ACL which decides, it's that every implementation can work
> with the ones created by other implementations. There's that weird
> problem with the dir recognized as socket, but that's something I'll
> look into at one point.
I did and found the problem. Please give the latest snapshot from
https://cygwin.com/snapshots/ a try.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-01-15 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 20:26 Corinna Vinschen
2016-01-13 8:14 ` random user
2016-01-13 15:33 ` Corinna Vinschen
2016-01-14 8:30 ` random user
2016-01-14 15:22 ` Corinna Vinschen
2016-01-15 17:27 ` Corinna Vinschen [this message]
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=20160115143433.GB12431@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).