public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.7
Date: Fri, 06 Nov 2015 14:51:00 -0000	[thread overview]
Message-ID: <563CBE56.8040809@cornell.edu> (raw)
In-Reply-To: <20151106125012.GA26566@calimero.vinschen.de>

On 11/6/2015 7:50 AM, Corinna Vinschen wrote:
> On Nov  6 12:12, Marco Atzeri wrote:
>> On 06/11/2015 10:26, Corinna Vinschen wrote:
>>> Hi Cygwin friends and users,
>>>
>>>
>>> I released a new TEST version of Cygwin, 2.3.0-0.7.
>>>
>>> =========================================================================
>>>
>>> IMPORTANT NOTE:
>>>
>>>    The upcoming official 2.3.0 release, which I'm planning for next
>>>    Monday, will not yet contain the below described ACL changes.  I got
>>>    not enough feedback from testers to be confident enough to put this
>>>    into a release.
>>>
>>>    When I release 2.3.0-1, I also immediately release a 2.4.0-0.1
>>>    test release to allow undisruptive testing of the new ACL code.
>>>
>>>    Please guys, I really need feedback for this stuff.
>>>
>>> =========================================================================
>>
>> Hi Corinna,
>> I have not seen anything strange until now;
>> however as a single user in a not domain environment
>> I doubt my task case is particularly meaningful.
>
> Thanks all the same!  One of the sore points is performance hit when
> using AuthZ to fetch the effective user permissions.  How's your
> impression?  Is it noticable in your environment?

I'm in the same situation as Marco.  I've been using the test releases, 
but only with local users, so it doesn't really test the main issues 
you're concerned about.  I haven't noticed any performance hit.

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

  reply	other threads:[~2015-11-06 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 10:09 Corinna Vinschen
2015-11-06 11:12 ` Marco Atzeri
2015-11-06 12:50   ` Corinna Vinschen
2015-11-06 14:51     ` Ken Brown [this message]
2015-11-06 19:35     ` Achim Gratz
2015-11-09 10:09       ` Corinna Vinschen
2015-11-06 16:30 ` Lemke, Michael  ST/HZA-ZIC2
2015-11-06 17:08   ` 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=563CBE56.8040809@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).