From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.4.7-1
Date: Sat, 17 Jun 2023 10:33:54 +0200 [thread overview]
Message-ID: <6feae4bf-c3db-ffd7-d909-4b514e608a84@towo.net> (raw)
In-Reply-To: <announce.20230616162552.879387-1-corinna-cygwin@cygwin.com>
Am 16/06/2023 um 16:25 schrieb Corinna Vinschen via Cygwin-announce via
Cygwin:
> The following packages have been uploaded to the Cygwin distribution:
>
> * cygwin-3.4.7-1
> * cygwin-devel-3.4.7-1
> * cygwin-doc-3.4.7-1
>
> Bug Fixes
> ---------
>
> - Fix CPU_SET(3) macro type mismatch by making the macros type-safe.
> Addresses https://cygwin.com/pipermail/cygwin/2023-March/253220.html
>
> - kill(1): don't print spurious error message.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-March/253291.html
>
> - Align behaviour of dirname in terms of leading slashes to POSIX:
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html
>
> - Fix reading CONIN$ in non cygwin apps when stdin is not a pty.
> Addresses https://cygwin.com/pipermail/cygwin/2023-April/253424.html
This does not fix the test case yes | more.com .
>
> - Fix bug in cygheap allocation size computation after fork. Addresses:
> https://cygwin.com/pipermail/cygwin-developers/2023-April/012620.html
>
> - Fix return value of ilogbl(NaN).
> Addresses: https://cygwin.com/pipermail/cygwin/2023-April/253511.html
>
> - Fix error handling in readlinkat.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-April/253510.html
>
> - Fix return code and errno set by renameat2, if oldfile and newfile
> refer to the same file, and the RENAME_NOREPLACE flag is set.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-April/253514.html
>
>
next prev parent reply other threads:[~2023-06-17 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 14:25 Corinna Vinschen via Cygwin-announce
2023-06-17 8:33 ` Thomas Wolff [this message]
2023-06-17 10:51 ` Takashi Yano
2023-06-17 10:57 ` Takashi Yano
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=6feae4bf-c3db-ffd7-d909-4b514e608a84@towo.net \
--to=towo@towo.net \
--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).