From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git for Windows 2.17.1(2)
Date: Tue, 29 May 2018 22:30:22 +0200 (DST) [thread overview]
Message-ID: <0MbOrg-1feKhn2Xv2-00Io4C@mail.gmx.com> (raw)
Dear Git users,
It is my pleasure to announce that Git for Windows 2.17.1(2) is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.17.0 (April 3rd 2018)
New Features
* Comes with Git v2.17.1.
* Comes with Perl v5.26.2.
* The installer now offers VS Code Insiders as option for Git's
default editor if it is installed.
* The vim configuration was modernized.
* Certain errors, e.g. when pushing failed due to a
non-fast-forwarding change, are now colorful.
* Comes with cURL v7.60.0.
* Comes with Git Credential Manager v1.16.1.
* Comes with Git LFS v2.4.2.
Bug Fixes
* Fixed an issue with recursive clone (CVE 2018-11235).
* This release really contains Git v2.17.1 (due to a bug in the release
automation, Git for Windows v2.17.1 did not actually include Git v2.17.1).
* Aliases that expand to shell commands can now take arguments
containing curly brackets.
* Ctrl+C is now handled in Git Bash in a sophisticated way: it
emulates the way Ctrl+C is handled in Git CMD, but in a
fine-grained way.
* Based on the the new Ctrl+C handling in Git Bash, pressing Ctrl+C
while git log is running will only stop Git from traversing the
commit history, but keep the pager running.
* Git was fixed to work correctly in Docker volumes inside Windows
containers.
* Tab completion of git status -- <partial-path> is now a lot faster.
* Git for Windows now creates directory symlinks correctly when asked
to.
* The option to disable revocation checks with Secure Channel which
was introduced in v2.16.1(2) now really works.
* Git no longer enters an infinite loop when misspelling git status
as, say, git Status.'
Filename | SHA-256
-------- | -------
Git-2.17.1.2-64-bit.exe | 64a44bf936dfb1af0ca8b84d5e9accb138452f1fa40030706964c3bbd9e1c69b
Git-2.17.1.2-32-bit.exe | 5dca054b53a2b38fbfc35f7b2390462d81f9ee62fa38b6f47d2d77365ab7f84a
PortableGit-2.17.1.2-64-bit.7z.exe | 5664ee470caf44743be1514c71f77cb8ac360dd69a667e6dd668cc6531acb8ba
PortableGit-2.17.1.2-32-bit.7z.exe | 74ef9dce2a185535dc5cbe7d53076df8558d739f29721be33b894d21b653f194
MinGit-2.17.1.2-64-bit.zip | 52e611a411cd58eaaab8218bb917cb4410b0c5733f234be6e581c6a9821b30ea
MinGit-2.17.1.2-32-bit.zip | 8ab37946bef8955a65f907d82483cb8a457f7404061ca59b8399d3623e9e691b
MinGit-2.17.1.2-busybox-64-bit.zip | f3aa489a67a600aefa8f20ee55f8977319bd3da568afaaadcd1b2e2cf21c575c
MinGit-2.17.1.2-busybox-32-bit.zip | 7c335e5ecd340a2980c9003bf8fefd73eb9553636c41ff1f9eae5dbb29bf6dde
Git-2.17.1.2-64-bit.tar.bz2 | b88192b92653df7bac19c87b18954ee5e1f513176633aca5ba0deaf51ad6e6f8
Git-2.17.1.2-32-bit.tar.bz2 | 4b284737e18d84b8a12b5138068f4fda7f9df93fa18ff5cde02d2b321cd943e5
pdbs-for-git-64-bit-2.17.1.2.a60968cf43-1.zip | b0e9961eab08a57a8a0f08620ea50cd4984c6f6f8bb48d66f3cfb872d9fea078
pdbs-for-git-32-bit-2.17.1.2.a60968cf43-1.zip | d902b96c155b243f4c8fa41056304ab6bc77763a1adef520a41cee97ca5f98c7
Ciao,
Johannes
reply other threads:[~2018-05-29 20:30 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=0MbOrg-1feKhn2Xv2-00Io4C@mail.gmx.com \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.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: 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 NNTP newsgroup(s).