From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: cygwin 3.1.5-1
Date: Mon, 01 Jun 2020 11:46:30 +0200 [thread overview]
Message-ID: <20200601114630.985195-1-corinna-cygwin@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygwin-3.1.5-1
* cygwin-devel-3.1.5-1
* cygwin-doc-3.1.5-1
This is a bugfix release, including a couple of nice to have changes
on top.
What changed:
-------------
- Support WSL symlinks. Create those by default now.
- FIFOs can now be opened multiple times for reading.
Bug Fixes:
----------
- Fix accidental evaluation of NUL (\0) characters in xterm console output.
Don't move cursor to the right in case of a NUL character in the console
output stream, this is not backed by terminfo.
Addresses: https://cygwin.com/ml/cygwin/2020-02/msg00162.html
- Fix a segfault when starting, e.g., mintty from a bash in a console
running xterm emulation.
Addresses: https://cygwin.com/ml/cygwin/2020-02/msg00197.html
- Fix TIOCINQ to always return number of inbound chars if available.
Addresses: https://cygwin.com/ml/cygwin/2020-02/msg00258.html
- Fix error handling in raw disk writes and allow full disk writes
including necessary locking on floppies as well.
Addresses: https://cygwin.com/pipermail/cygwin/2020-April/244610.html
- Fix several FIFO bugs.
Addresses: https://sourceware.org/pipermail/cygwin/2020-March/000206.html
https://sourceware.org/pipermail/cygwin/2020-April/244518.html
- Make sure pseudo tty doesn't hang if cygwin-console-helper.exe is
non-functional.
Addresses: https://cygwin.com/pipermail/cygwin-patches/2020q2/010191.html
- Fix a bug causing FIFOs to have incorrect permissions.
Addresses: https://sourceware.org/pipermail/cygwin/2020-May/245031.html
reply other threads:[~2020-06-01 9:48 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=20200601114630.985195-1-corinna-cygwin@cygwin.com \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-announce@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).