public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin/main] Cygwin: Fix latest release message being in the wrong release file. Date: Tue, 4 Jul 2023 14:51:12 +0000 (GMT) [thread overview] Message-ID: <20230704145112.5DD6C3858D35@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=e38f91d5a96c4554c69c833243e5afec8e3e90eb commit e38f91d5a96c4554c69c833243e5afec8e3e90eb Author: Corinna Vinschen <corinna@vinschen.de> AuthorDate: Tue Jul 4 16:50:00 2023 +0200 Commit: Corinna Vinschen <corinna@vinschen.de> CommitDate: Tue Jul 4 16:50:37 2023 +0200 Cygwin: Fix latest release message being in the wrong release file. Fixes: 6422e76637d3 ("Cygwin: Make <sys/cpuset.h> safe for c89 compilations") Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Diff: --- winsup/cygwin/release/3.4.7 | 3 --- winsup/cygwin/release/3.4.8 | 5 +++++ 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/winsup/cygwin/release/3.4.7 b/winsup/cygwin/release/3.4.7 index 923408ec2dce..0e6922163aa3 100644 --- a/winsup/cygwin/release/3.4.7 +++ b/winsup/cygwin/release/3.4.7 @@ -25,6 +25,3 @@ Bug Fixes - 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 - -- Make <sys/cpuset.h> safe for c89 compilations. - Addresses: https://cygwin.com/pipermail/cygwin-patches/2023q3/012308.html diff --git a/winsup/cygwin/release/3.4.8 b/winsup/cygwin/release/3.4.8 new file mode 100644 index 000000000000..d1e34ce3c633 --- /dev/null +++ b/winsup/cygwin/release/3.4.8 @@ -0,0 +1,5 @@ +Bug Fixes +--------- + +- Make <sys/cpuset.h> safe for c89 compilations. + Addresses: https://cygwin.com/pipermail/cygwin-patches/2023q3/012308.html
reply other threads:[~2023-07-04 14:51 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=20230704145112.5DD6C3858D35@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ /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: linkBe 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).