From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Updated: Cygwin 2.2.1-1
Date: Thu, 20 Aug 2015 11:14:00 -0000 [thread overview]
Message-ID: <announce.20150820111329.GA17895@calimero.vinschen.de> (raw)
Hi Cygwin friends and users,
I released another version of Cygwin. The version number is 2.2.1-1.
Bug Fixes
---------
- Revert the following patch from 2.2.0:
When started from a non-Cygwin process, check if $HOME starts with a
slash (absolute POSIX path). Otherwise ignore it.
Addresses discussion starting at
https://cygwin.com/ml/cygwin/2015-08/msg00048.html
- Fix output of /proc/cpuinfo in terms of cpu topology and cache size for
modern CPUs and modern Windows OSes supporting more than 64 logical CPUs.
Addresses: https://cygwin.com/ml/cygwin/2015-06/msg00345.html
- Don't call LsaLookupSids to fetch group information and don't perform RFC2307
owner/group mapping on Samba/NFS if account info is only fetched from local
passwd/group files.
Addresses: https://cygwin.com/ml/cygwin/2015-07/msg00270.html
- Precautionally fix a potential data corruption problem in pipe I/O, only
actually observered in Wine yet. However, MSDN language indicates this
might be a problem on real Windows as well.
Addresses: https://cygwin.com/ml/cygwin/2015-08/msg00225.html
- Include <sys/ucontext.h> from <sys/signal.h> if compiling for POSIX.1-2008.
Addresses: https://cygwin.com/ml/cygwin/2015-08/msg00266.html
- getservent(3) returned the port number in host byte order. Change that to
network byte order as required.
Addresses: https://cygwin.com/ml/cygwin/2015-08/msg00301.html
Have fun,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
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-08-20 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=announce.20150820111329.GA17895@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).