From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-patches@cygwin.com
Subject: [PATCH] Cygwin: add 3.3.5 release notes
Date: Sat, 5 Mar 2022 11:27:10 +0900 [thread overview]
Message-ID: <20220305022710.13179-1-takashi.yano@nifty.ne.jp> (raw)
---
winsup/cygwin/release/3.3.5 | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 winsup/cygwin/release/3.3.5
diff --git a/winsup/cygwin/release/3.3.5 b/winsup/cygwin/release/3.3.5
new file mode 100644
index 000000000..11698c4e4
--- /dev/null
+++ b/winsup/cygwin/release/3.3.5
@@ -0,0 +1,30 @@
+Bug Fixes
+---------
+
+- Fix a bug that accessing UNC path mounted to a drive letter using
+ SMB3.11 fails with error "Too many levels of symbolic links.".
+
+- Fix a console bug that escape sequence IL/DL (CSI Ps L, CSI Ps M)
+ does not work correctly at the last line.
+ Addresses: https://cygwin.com/pipermail/cygwin/2022-February/250736.html
+
+- Fix a problem that ENABLE_INSERT_MODE and ENABLE_QUICK_EDIT_MODE
+ flags are cleared if cygwin is started in console.
+
+- Fix an issue that cmd.exe also is terminated along with the cygwin
+ app started from the cmd.exe if the cygwin app is terminated by
+ Ctrl-C.
+
+- Fix deadlock caused when keys are typed in pty while a lot of text
+ output.
+
+- Fix a problem that the console mode for input is not set correctly
+ when non-cygwin app is started with stdin redirected.
+ Addresses:
+ https://github.com/GitCredentialManager/git-credential-manager/issues/576
+
+- Fix exit code when non-cygwin app is terminated by Ctrl-C.
+
+- Fix a bug that the order of the console key inputs are occasionally
+ swapped, especially when CPU load is high.
+ Addresses: https://cygwin.com/pipermail/cygwin/2022-February/250957.html
--
2.35.1
reply other threads:[~2022-03-05 2:27 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=20220305022710.13179-1-takashi.yano@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-patches@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).