public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: handling invalid user/groups (was  incompat in cygwin choice of using '+' as domain and user separator.)
Date: Wed, 05 Sep 2018 08:04:00 -0000	[thread overview]
Message-ID: <20180905080322.GB22010@calimero.vinschen.de> (raw)
In-Reply-To: <5B8EE652.1090804@tlinx.org>

[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]

On Sep  4 13:08, L A Walsh wrote:
> On 8/27/2018 10:26 AM, Corinna Vinschen wrote:
> 
> On 8/27/2018 3:50 AM, Corinna Vinschen wrote:
> > The only sane way to handle unknown SIDs in file ACLs is to ignore them
> > entirely.  The result will be that you never see them in getfacl, nor
> > will they be stored by tar or rsync.  They are just not there from the
> > Cygwin perspective.
> ---
> 	Sounds fine to me...
> 
> > I created a patch, uploaded developer snapshots to
> > https://cygwin.com/snapshots/ and released a new Cygwin test
> > release 2.11.0-0.4 with this change.  Please giver any of
> > them a try.
> 
> does the latest cygwin also have this patch

No, I deliberately removed it from the released version to tease you.

> p.s. -- some "FYI" stuff about your email:
>        when i respond to one of your emails, I get two (2)        "To:"
> entries -- both to cygwin@cygwin.com.
> 	I think it might be because the emails from you contain
> 	two 'Mail-Followup-To:' lines -- see below**.

I only add a reply-to.  I have no idea where the followup to's are
generated.


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: 833 bytes --]

  reply	other threads:[~2018-09-05  8:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23  8:14 incompat in cygwin choice of using '+' as domain and user separator L A Walsh
2018-08-23 14:35 ` cyg Simple
2018-08-23 16:39   ` Corinna Vinschen
2018-08-23 15:59 ` Corinna Vinschen
2018-08-27 10:50   ` L A Walsh
2018-08-27 13:53     ` Corinna Vinschen
2018-08-27 17:26       ` Corinna Vinschen
2018-08-27 17:27         ` Corinna Vinschen
2018-08-27 22:47           ` Corinna Vinschen
2018-09-04 20:08             ` handling invalid user/groups (was incompat in cygwin choice of using '+' as domain and user separator.) L A Walsh
2018-09-05  8:04               ` Corinna Vinschen [this message]
2018-09-06  0:25                 ` L A Walsh
2018-09-05 11:35               ` Andrey Repin
2018-09-05 23:57                 ` Odd email symptoms (was Re: handling invalid user/groups) L A Walsh

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=20180905080322.GB22010@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).