From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [ANNOUNCE] Git for Windows 2.11.0
Date: Thu, 1 Dec 2016 13:31:30 +0100 [thread overview]
Message-ID: <20161201123130.7608-1-johannes.schindelin@gmx.de> (raw)
MIME-Version: 1.0
Fcc: Sent
Dear Git users,
It is my pleasure to announce that Git for Windows 2.11.0 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.10.2 (November 2nd 2016)
New Features
* Comes with Git v2.11.0.
* Performance of git add in large worktrees was improved.
* A new, experimental, builtin version of the difftool is available
as an opt-in feature.
* Support has been added to generate project files for Visual Studio
2010 and later.
Bug Fixes
* The preload-index feature now behaves much better in conjunction
with sparse checkouts.
* When encountering a symbolic link, Git now always tries to read it,
not only when core.symlinks = true.
* The regression where Git would not interpret non-ASCII characters
passed from a CMD window correctly has been fixed.
* Performance of the cache of case-insensitive file names has been
improved.
* When building with MS Visual C, release builds are now properly
optimized.
* git cvsexportcommit now also works with CVSNT.
* Git's Perl no longer gets confused by externally-set PERL5LIB.
* The uninstaller no longer leaves an empty Git\mingw64 folder behind
.
* The installer now actually records whether the user chose to enable
or disable the Git Credential Manager.
* A certain scenario that could cause a crash in cherry-pick no
longer causes that.
Filename | SHA-256
-------- | -------
Git-2.11.0-64-bit.exe | fd1937ea8468461d35d9cabfcdd2daa3a74509dc9213c43c2b9615e8f0b85086
Git-2.11.0-32-bit.exe | 2a6083479538c4fe454336660fce96346ee3cf46f99ce08a666d4635539239d7
PortableGit-2.11.0-64-bit.7z.exe | a86cc4babfe204cc91408053b517827b4a93e6c659b85ab30910eda0e38bfc19
PortableGit-2.11.0-32-bit.7z.exe | fccec9350c1cb58a5e6d84d307d4f9f43ab9d58d93c8de67056416539d199002
MinGit-2.11.0-64-bit.zip | f31b0135e11e425555fb34779da3345ce8d32490fdd0a33b6f5ae8d74bae20b6
MinGit-2.11.0-32-bit.zip | 48e363cb6ce867a8004056a95da57f7c330ab79dbd26e4895c2aaeb4aec3b3a0
Git-2.11.0-64-bit.tar.bz2 | e62263ff734dbb071819dfcc33e9f443f9a445cde54d0102f6d164d5df5ece6c
Git-2.11.0-32-bit.tar.bz2 | 43dda49d4c7305d18b9f0612f66ba096ca2881a8ebf7b41cfb358d9a05fedef9
Ciao,
Johannes
next reply other threads:[~2016-12-01 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 12:31 Johannes Schindelin [this message]
2016-12-01 14:12 ` [ANNOUNCE] Git for Windows 2.11.0 stefan.naewe
2016-12-01 17:05 ` Johannes Schindelin
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=20161201123130.7608-1-johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@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).