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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to