public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] cygwin 3.1.4-1
Date: Wed, 19 Feb 2020 11:04:00 -0000	[thread overview]
Message-ID: <announce.20200219115927.387179-1-corinna-cygwin@cygwin.com> (raw)

The following packages have been uploaded to the Cygwin distribution:

* cygwin-3.1.4-1
* cygwin-devel-3.1.4-1
* cygwin-doc-3.1.4-1

We skipped the 3.1.3 release due to technical reasons, nothing to
worry about.

This is a bugfix release, including a couple of nice to have changes
on top.


What changed:
-------------

- Allow symlinks to be opened with O_PATH | O_NOFOLLOW.

- Allow the pathname argument to readlinkat(2) to be an empty string,
  provided the dirfd argument refers to a symlink opened with
  O_PATH | O_NOFOLLOW.  The readlinkat call then operates on that
  symlink.

- Support the Linux-specific AT_EMPTY_PATH flag for fchownat(2) and
  fstatat(2).

- Allow AF_LOCAL sockets to be opened with O_PATH.

- <signal.h>: New macro _NSIG replacing NSIG.  NSIG is now only
  visible to MISC builds, as on Linux.

- The new locale modifier @cjksingle allows enforcing of single-width
  character property for usually double-widthed characters.  This will
  be supported by upcoming mintty releases.  For the reasoning, see
  https://gitlab.freedesktop.org/terminal-wg/specifications/issues/9.


Bug Fixes:
----------

- Define CPU_SETSIZE, as on Linux.
  Addresses: https://cygwin.com/ml/cygwin/2019-12/msg00248.html

- Fix a regression that prevented the root of a drive from being the
  Cygwin installation root.
  Addresses: https://cygwin.com/ml/cygwin/2020-01/msg00111.html

- Many fixes in new pseudo console support.
  Addresses (among others):
	     https://cygwin.com/ml/cygwin/2019-12/msg00173.html
	     https://cygwin.com/ml/cygwin/2019-12/msg00292.html
	     https://cygwin.com/ml/cygwin/2019-12/msg00295.html
	     https://cygwin.com/ml/cygwin/2020-01/msg00093.html
	     https://cygwin.com/ml/cygwin/2020-01/msg00147.html
	     https://cygwin.com/ml/cygwin/2020-01/msg00161.html

--
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:[~2020-02-19 11:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 11:04 Corinna Vinschen [this message]
2020-02-19 17:02 ` howto rollback cygwin 3.1.4-1 to older 3.0.7 version? Eugene Klimov
2020-02-19 18:11   ` Marco Atzeri
2020-02-19 18:43     ` Marco Atzeri
2020-02-20  4:01       ` Eugene Klimov
2020-02-20  9:13         ` Thomas Wolff
2020-02-20  9:52           ` Eugene Klimov
2020-02-20 10:31             ` Takashi Yano
2020-02-20 12:02               ` Eugene Klimov
2020-02-20  3:55     ` Eugene Klimov
2020-02-19 23:52   ` Takashi Yano
2020-02-20  4:51     ` Eugene Klimov
2020-02-20 10:25       ` Takashi Yano
2020-02-20 12:05         ` Eugene Klimov
2020-02-24  8:02   ` Houder
2020-02-19 20:30 ` mintty hangs when started from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.4-1) Achim Gratz

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.20200219115927.387179-1-corinna-cygwin@cygwin.com \
    --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).