From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: setfacl -s acl_entries file file ... now fails
Date: Thu, 12 Feb 2015 18:29:00 -0000 [thread overview]
Message-ID: <20150212180041.GC7818@calimero.vinschen.de> (raw)
In-Reply-To: <f693c1a646e96a35da21600dbb5983e0.squirrel@webmail.xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Feb 12 16:06, Houder wrote:
> Hi Corinna,
>
> Regression? setfacl -s used to accept multiple file arguments ... (yes, I am sure)
>
> @@ touch aap noot mies
> @@ ls -l aap noot mies
> -rw-r--r-- 1 Henri None 0 Feb 12 15:55 aap
> -rw-r--r-- 1 Henri None 0 Feb 12 15:55 mies
> -rw-r--r-- 1 Henri None 0 Feb 12 15:55 noot
> @@ setfacl -s u::rwx,g::r-x,o:r-x aap noot mies
> setfacl: Invalid argument
> setfacl: Invalid argument
Yes, regression. When revamping the acl(SETACL, ...) call I used
the a_type value in the incoming aclent_t entry for bookkeeping,
thus invalidating it for further reuse. I fixed that in CVS and
uploaded a new snapshot on https://cygwin.com/snapshots/
Please give it a try.
Btw., it's really not necessary to address me directly in the subject of
a mail to this list. I am reading this list regulary and I'm not
ignoring reports which look like a bug in Cygwin and least of all those
with testcases. In fact, I'd prefer a subject not calling me out.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-12 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 16:34 setfacl -s acl_entries file file ... now fails ... Corinna? Houder
2015-02-12 18:29 ` Corinna Vinschen [this message]
2015-02-13 2:12 ` setfacl -s acl_entries file file ... now fails Houder
2015-02-13 9:23 ` 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=20150212180041.GC7818@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).