From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Git for Windows Mailing List <git-for-windows@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Announcing Git for Windows 2.6.0
Date: Tue, 29 Sep 2015 23:03:28 +0200 [thread overview]
Message-ID: <3dba113ea1ed82a6e5e745a3d69dceaa@dscho.org> (raw)
Dear Git users,
it is my pleasure to announce that Git for Windows 2.6.0 is available (see https://git-for-windows.github.io/ for details and download links).
Thank you, contributors!
Changes since Git for Windows 2.5.3 (September 18th 2015)
New Features
• Comes with Git 2.6.0
• The WhoUses.exe tool to determine which process holds a lock on a
given file (which was shipped with Git for Windows 1.x) gets
installed alongside Git for Windows again.
• The values CurrentVersion, InstallPath and LibexecPath are added to
the HKEY_LOCAL_MACHINE\Software\GitForWindows registry key to help
third-party add-ons to find us.
• When fetching or pushing with Git without a console, we now fall
back to Git GUI's askpass helper to ask for pass phrases.
• When run through <INSTALL_PATH>\cmd\git.exe, Git will find tools in
$HOME/bin now.
Bug Fixes
• The portable version avoids DLL search path problems even when
installed into a FAT filesystem.
• Configuring notepad as editor without configuring a width for
commit messages no longer triggers an error message.
• When using Windows' default console for Git Bash, the .sh file
associations work again.
• Portable Git's README is now clearer about the need to run
post-install.bat when unpacking manually.
• We use the winpty trick now to run ipython interactively, too.
• When the environment variable HOME is not set, we now fall back
correctly to use HOMEDRIVE and HOMEPATH.
• The home directory is now set correctly when running as the SYSTEM
user.
• The environment variable GIT_WORK_TREE may now differ in lower/
upper case with the Git's idea of the current working directory.
• Running git clone --dissociate ... no longer locks the pack files
during the repacking phase.
• Upstream cURL fixes for NTLM proxy issues ("Unknown SSL error")
were backported.
Ciao,
Johannes
reply other threads:[~2015-09-29 21:03 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=3dba113ea1ed82a6e5e745a3d69dceaa@dscho.org \
--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).