Announcing Git for Windows 2.5.2

224 views
Skip to first unread message

Johannes Schindelin

unread,
Sep 10, 2015, 4:47:29 PM9/10/15
to Git for Windows Mailing List, Git Mailing List
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

瀬川晃一

unread,
Sep 12, 2015, 5:40:42 AM9/12/15
to git-for-windows, g...@vger.kernel.org
When you install the 2.5.2 window10 64 -bit , it is an error that there is no myxxx of 64bit when Git GUI execution .

2015年9月11日金曜日 5時47分29秒 UTC+9 Johannes Schindelin:

Johannes Schindelin

unread,
Sep 12, 2015, 6:03:42 AM9/12/15
to 瀬川晃一, git-for-windows
Hi,

On 2015-09-12 05:01, 瀬川晃一 wrote:
> When you install the 2.5.2 window10 64 -bit , it is an error that there
> is
> no myxxx of 64bit when Git GUI execution .

Hmm. I do not quite understand. But I *guess* that you are referring to
the problem described in this ticket:
https://github.com/git-for-windows/git/issues/376

In short: I will release an updated installer soon, with other fixes. In
the meantime, as a work-around you could right-click on the Git GUI
shortcut (you can right-click the icon in the Windows menu and open the
file location to get there), select Properties... and change the Target:
from

"C:\Program Files\Git\cmd\git-gui.exe"

to

"C:\Program Files\Git\cmd\git.exe" gui

It will open an ugly, unnecessary console until the next Git for Windows
version is available, but at least it will work until then.

Ciao,
Johannes

瀬川晃一

unread,
Sep 12, 2015, 8:47:14 AM9/12/15
to git-for-windows, g...@vger.kernel.org
Thank you , Ciao, Johannes. Nature of the error C: / Windows /.../ cmd / mingw64 can not be found . It was that . I'm sorry for not properly fill . It was movement After you copy the mingw64 directly under cmd according to the error . We are looking forward to the new release .


2015年9月11日金曜日 5時47分29秒 UTC+9 Johannes Schindelin:
Dear Git users,

Marko Palola

unread,
Sep 12, 2015, 5:58:42 PM9/12/15
to git-for-windows, g...@vger.kernel.org

Hi

I have some problems with 2.5.2 and 2.5.1 and bitdefender scanner.
but I can use v2.5.0


BR
 Marko

Johannes Schindelin

unread,
Sep 12, 2015, 6:56:33 PM9/12/15
to Git for Windows Mailing List, Git Mailing List
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

Johannes Schindelin

unread,
Sep 12, 2015, 7:00:00 PM9/12/15
to Marko Palola, git-for-windows, g...@vger.kernel.org
Hi Marko,

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

> I have some problems with 2.5.2 and 2.5.1 and bitdefender scanner.
> but I can use v2.5.0

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
Reply all
Reply to author
Forward
0 new messages