From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 46362 invoked by alias); 11 Apr 2015 14:52:27 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 46353 invoked by uid 89); 11 Apr 2015 14:52:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 11 Apr 2015 14:52:26 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id D163EA80A4C; Sat, 11 Apr 2015 16:52:23 +0200 (CEST) Date: Sat, 11 Apr 2015 14:52:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1 Message-ID: <20150411145223.GK7343@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="v2Uk6McLiE8OV1El" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-04/txt/msg00210.txt.bz2 --v2Uk6McLiE8OV1El Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1491 Hi Henri, On Apr 11 15:25, Houder wrote: > Hi Corinna, >=20 > Reference: https://cygwin.com/ml/cygwin/2015-04/msg00201.html > - [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1 I really appreciate bug reports, but, please, try to keep the threading intact. Please reply to mails rather than creating new threads which have no connection to the original threads. Or if so, at least set the "In-Reply-To:" Header field correctly. By additionally changing the subject you're making searching the archives unnecessarily hard for others. I changed the subject back. > Sorry, Corinna, but I have to ask: will this be the correct behaviour of = Cygwin > from now on? ... because I am very much surprised ... It's what we haxxers call "a bug". I made a typo in another function, copy-pasted the code over to the chmod function, fixed it in the original function and then forgot to fix it in chmod. Btw., the output from SetACL isn't that helpful, because it doesn't add information to what icacls already delivers. What I'd be more interested in is the output of our own getfacl in conjunction with icacls. It allows me to see the POSIX ACL the internal ACL reading routine created from the Windows ACL. I just uploaded a new test release 2.0.0-0.2. It's supposed to fix this bug. Give it a bit of time to hit the mirrors. Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --v2Uk6McLiE8OV1El Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVKTUnAAoJEPU2Bp2uRE+gJuUP/AzaFIZp2724GuZTtJ998+MK omI7x385YOTZo33C3iIyiJYEdo2POePVna0FMs8/IudIcLM9Cb0M2wEI08ysIJQ1 1A6ieBgB+ntHNSg/TV+76vhWul8cNbV8VwOFpHymqpCnZs75uAZY/WcazJJGJ5er pvEsg0hSsMamUu1x4kSFzPuVq9z77VnP5LNreDyxmPyEuwJHvfPgx7ByxeWZYOo+ 5/A118P1JZuEKCPDgkKoUcko5jWSIDc6jwwcVu3zXrOmzZRVaaxPjew6/Kv3wbsa pAMk4Ag3JIKHthsQQFm8AqDqDBW1oRSfl0etAnkFiOdi39a7i6KJg8rYPTONf32V Bs6IyDlaskPPzKJ7ObPNZXp8aqJTdz7GAEI+vI96Tnmd0Lqoa4+Fah1wMVm5wyy5 go/NMwiBVZ7FE6Y20rn0INOwt9LzA3yEopWhju+dPlxzQZiT/U4Ciql99IL/4WqB 8AfXmH5cICC0cSqT+PPonB6nQJHfJjuhalbjxNA0/PxXKCJjSvew8QfkkNVhucdo PMJyZRi78ABaX65cqZQo9GB0o/2l8pCA57LryfhQKhvhwRco16YbbweJhyv5VQ/a YkAXXS+Mvd0ecaM6rXPMpVkJ6925FyNJWcy97jCKieZ6WpAaN3qnXvj54tv7xYNp Td8i41yN5DIEJKquTVMR =xF4L -----END PGP SIGNATURE----- --v2Uk6McLiE8OV1El--