From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: Updated: setup.exe (Release 2.871)
Date: Fri, 29 May 2015 13:53:00 -0000 [thread overview]
Message-ID: <20150529135159.GA25145@calimero.vinschen.de> (raw)
Hi folks,
A new version of Setup, release 2.871, 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.870:
- Improved performance in terms of SHA512 checksum computation.
- Add a "Retry" button to the "File in use" dialog.
- Avoid truncation of "Bin?" and "Src? columns in package chooser.
- Various under-the-hood optimizations of log output.
Please send bug reports, as usual, to the public mailing list
cygwin AT cygwin DOT com.
Have fun,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
reply other threads:[~2015-05-29 13:53 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=20150529135159.GA25145@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).