public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: win dirs don't handle lack of inherited rule(?): getfacl + tar dir  Warning: Cannot acl_to_text: Invalid argument
Date: Sun, 10 Mar 2019 23:15:00 -0000	[thread overview]
Message-ID: <5C859AA1.9070307@tlinx.org> (raw)
In-Reply-To: <951349031.20190311013719@yandex.ru>

I'll have to try it, just haven't finished responding to
the replies yet -- keep getting distracted... ;-)

On 3/10/2019 3:37 PM, Andrey Repin wrote:
>> I would not doubt that icacls would refuse to create
>> mis-ordered ACL's, for example.
> 
> Again, you'd be surprised.
> 
>> I.e. its likely a non-windows
>> program or odd interaction between one and windows.

--
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

  reply	other threads:[~2019-03-10 23:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08  3:36 L A Walsh
2019-03-08 12:15 ` Corinna Vinschen
2019-03-10 10:48   ` L A Walsh
2019-03-10 11:20     ` Corinna Vinschen
2019-03-10 13:35     ` Andrey Repin
2019-03-10 16:38       ` L A Walsh
2019-03-10 22:50         ` Andrey Repin
2019-03-10 23:15           ` L A Walsh [this message]
2019-03-10 14:09     ` Brian Inglis
2019-03-12 15:45       ` L A Walsh
2019-03-12 16:36         ` Corinna Vinschen
2019-03-13  2:22           ` L A Walsh
2019-03-13  9:19             ` Corinna Vinschen
2019-03-13  9:32               ` Corinna Vinschen
2019-03-13 11:34                 ` Corinna Vinschen
2019-03-15  2:46                   ` L A Walsh
2019-03-15  9:17                     ` Corinna Vinschen
2019-03-15 12:25                   ` Brian Inglis
2019-03-15 13:34                     ` Corinna Vinschen
2019-03-15 14:46                       ` L A Walsh
2019-03-15 14:52                         ` 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=5C859AA1.9070307@tlinx.org \
    --to=cygwin@tlinx.org \
    --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).