Git for Windows 2.6.1

Changes since Git for Windows 2.6.1 (September 29th 2015)

New Features

• Comes with Git 2.6.1
• The installer now writes the file /etc/install-options.txt to record which options were chosen at install time.
• Replaces git flow with the AVH edition which is maintained actively, in surprising and disappointing contrast to Vincent Driessen's very own project.

Bug Fixes

• The PATH variable is now really left alone when choosing the "Use Git from Git Bash only" option in the installer. Note that upgrading Git for Windows will call the previous version's uninstaller, which might still have that bug.
• Git GUI's Registry>Create Desktop Icon now generates correct shortcuts.
• The antiword utility to render Word documents for use in git diff now works correctly.
• In 64-bit installations, we no longer set a pack size limit by default.
• When installing Git for Windows as regular user, the installer no longer comptries to create privileged registry keys.

Git for Windows 2.6.0

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.

Git for Windows 2.5.3

Changes since Git-2.5.2(2) (September 13th 2015)

New Features

• Comes with Git 2.5.3.
• Includes git flow.
• By configuring git config core.editor notepad, users can now use notepad.exe as their default editor. Configuring git config format.commitMessageColumns 72 will be picked up by the notepad wrapper and line-wrap the commit message after the user edited it.
• The Subversion bindings for use with git svn were upgraded to version 1.9.1.
• Some interactive console programs, e.g. psql.exe, now work in mintty thanks to pre-configured aliases.
• The mechanism to diff .pdf, .doc and .docx files known from Git for Windows 1.x has been ported to Git for Windows 2.x.
• Git can now access IPv6-only hosts via HTTP/HTTPS.

Bug fixes

• The .vimrc in the home directory is now allowed to have DOS line endings.
• The README.portable file of the portable Git mentions the need to run post-install.bat when the archive was extracted manually.
• Home directories for user names with non-ASCII characters are handled correctly now.
• The documentation no longer shows plain-text linkgit:... "links" but proper hyperlinks instead.
• The mtab link is written to /etc/mtab again, as it should.
• When run inside the PowerShell, Git no longer gets confused when the current directory's path and what is recorded in the file system differs in case (e.g. "GIT/" vs "Git/").

Git for Windows 2.5.2 (Release 2)

This release primarily fixes the Git GUI regression that was introduced into Git for Windows 2.5.2. In addition, the following bugs have been fixed:

• It now works to call git add -p -- . when there is a large number of files.
• The Arrow keys can be used in the Bash history again when run in the Windows console.
• Tab completion in the context of a large Active Directory is no longer slow.

Git for Windows 2.5.2

Changes since Git-2.5.1 (August 31th 2015)

New Features

• Comes with Git 2.5.2
• Alternates can now point to UNC paths, i.e. network drives.

Bug fixes

• The MSys2 runtime was taught not to look hard for groups, speeding up Git Bash's startup time.
• A work around was added for issues when installing 32-bit Git for Windows on 64-bit Windows 10.
• The installer no longer freezes when there are interactive commands in the user's .profile.
• git rebase --skip was speeded up again.
• The redirector in /bin/bash.exe now adjusts the PATH environment variable correctly (i.e. so that Git's executables are found) before launching the real Bash, even when called without --login.
• When installing Git for Windows to a location whose path is longer than usual, Git commands no longer trigger occasional Bad address errors.
• Git no longer asks for a DVD to be inserted again when one has been ejected from the D: drive.

Git for Windows 2.5.1

Apart from being based on Git 2.5.1, this Git for Windows release brings the following bug fixes:

• Backspace works now with
  ConHost-based (cmd.exe) terminal.
• When there is a ~/.bashrc but no ~/.bash_profile, the latter will be created automatically.
• When calling a non-login shell, the prompt now works.
• The text in the installer describing the terminal emulator options is no longer cut off.
• The connect.exe tool to allow SSH connections via HTTP/HTTPS/SOCKS proxies is included in Git for Windows again, as it was in Git for Windows 1.x.
• The LANG variable is no longer left unset (which caused troubles with vim).
• call start-ssh-agent no longer spits out bogus lines.
• It is now possible even behind NTLM-authenticated proxies to install Git for Windows' SDK.
• We can handle the situation now when the first $PATH elements point outside of Git for Windows' bin/ directories and contain .dll files that interfere with our own (e.g. PostgreSQL's libintl-8.dll).
• The patch tool is now included again as it was in Git for Windows 1.x.

Git for Windows 2.5.0

This is the first official version of Git for Windows (i.e. the first release without the -preview suffix).

It would not have been possible without substantial support of GitHub, in particular Michael Haggerty, Jeff King and Brendan Forster, the help of Karsten Blees, Nalla, Sebastian Schuberth, and other contributors including Microsoft.

Fifth release candidate of Git for Windows

Apart from synchronizing with Git 2.4.6, this version brings the following fixes:

• Git for Windows handles symlinks now, even if core.symlinks does not tell Git to generate symlinks itself.
• git svn learned not to reuse incompatible on-disk caches left over from previous Git for Windows versions.

Fourth release candidate of Git for Windows 2.x

Apart from synchronizing with Git 2.4.5, this release candidate fixes a critical bug that prevented GitHub for Windows from using Git for Windows 2.x for its command-line tools.

Third release candidate of Git for Windows 2.x

New Features

• Comes with Git 2.4.4
• The POSIX-to-Windows path mangling can now be turned off by setting the MSYS_NO_PATHCONV environment variable. This even works for individual command lines: MSYS_NO_PATHCONV=1 cmd /c dir /x will list the files in the current directory along with their 8.3 versions.

Bug fixes

• git-bash.exe no longer changes the working directory to the user's home directory.
• Git can now clone into a drive root, e.g. C:\.
• For backwards-compatibility, redirectors are installed into /bin/bash.exe and /bin/git.exe, e.g. to support SourceTree and TortoiseGit better.
• When using core.symlinks = true while cloning repositories with symbolic links pointing to directories, git status no longer shows bogus modifications.