From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: Updated: setup (2.897)
Date: Tue, 26 Mar 2019 16:42:00 -0000 [thread overview]
Message-ID: <f1993347-721c-15ca-758d-c509614eb411@dronecode.org.uk> (raw)
A new version of Setup (2.897) has been uploaded to:
https://cygwin.com/setup-x86.exe (32 bit version)
https://cygwin.com/setup-x86_64.exe (64 bit version)
Changes compared to 2.895:
- Use 'kill -W' when killing processes (needed with Cygwin 3.0.0, since
Windows and Cygwin PIDs are completely decoupled)
- Suppress FTP 550 error MessageBox for (expected) missing setup.zst
Addresses: https://cygwin.com/ml/cygwin/2019-02/msg00153.html
- Don't propagate actions down category tree into obsolete categories
Addresses: https://cygwin.com/ml/cygwin/2019-01/msg00132.html
- Double-click in 'New' column now toggles between the current state and
installing the preferred version, if different
Addresses: https://cygwin.com/ml/cygwin/2018-12/msg00123.html
Please send bug reports, as usual, to the public mailing list cygwin AT
cygwin DOT com.
reply other threads:[~2019-03-26 16:42 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=f1993347-721c-15ca-758d-c509614eb411@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-announce@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).