Announcing Git for Windows 2.5.2

Dear Git users,

it is my pleasure to announce Git for Windows 2.5.2. The installers and portable versions can be downloaded from our home page at https://git-for-windows.github.io/.

We have been quite busy, lots of contributions (mostly bug reports, but also the occasional Pull Request). Thank you all! The changes since Git for Windows 2.5.1 are:

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.

Ciao, Johannes

Dear Git users,

you probably noticed that there was a really obvious bug in the "Git GUI" entry in the Start Menu (because it has been reported several times).

I just released a new version that squashes this bug and three more. Please find it here:

    https://github.com/git-for-windows/git/releases/tag/v2.5.2.windows.2

In case you encounter a bug, please follow the guide lines on our wiki: https://github.com/git-for-windows/git/wiki/Issue-reporting-guidelines

Ciao, Johannes

Hi Marko,

On 2015-09-12 20:46, Marko Palola wrote:

We have had plenty of reports since the start of the Git for Windows project in 2007. None of them have turned out to be true viruses, all of them were caused by flawed virus scanners.

Further, I build these executables and installers on a trusted machine that is used exclusively for the development and maintenance of Git for Windows.

So I am inclined to dismiss *any* such report, especially when it comes with no concrete evidence that there is indeed a virus present.

Ciao, Johannes