This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
New git.exe wrapper do not return correctly #43
Description
Hello. Hope I report this correctly.
Just installed Git-1.7.11-preview20120704.exe and can see an issue with git.exe wrapper, where it returns 1, instead of 0.
From a new install on a windows xp machine without any git installation before.
Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.Y:>echo %errorlevel%
0
Y:>git --version
git version 1.7.11.msysgit.1
Y:>echo %errorlevel%
1
Y:>
On a windows 7 64 bit, just upgraded to 1.7.11.1, and still have the old git.cmd wrapper.
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Users\cst>echo %errorlevel%
0
C:\Users\cst>git.cmd --version
git version 1.7.11.msysgit.1
C:\Users\cst>echo %errorlevel%
0
C:\Users\cst>git.exe --version
git version 1.7.11.msysgit.1
C:\Users\cst>echo %errorlevel%
1
C:\Users\cst>
Activity
t00 commentedon Jul 6, 2012
I can confirm this issue with "git.exe fetch -v --progress "origin" master:remotes/origin/master".
ERORLEVEL 1 is returned on successful execution.
git-wrapper: ensure the child process exit code is returned.
Siarhei-Yarkavy commentedon Jul 9, 2012
Guys I did update today for new version and catch this issue. The problem that Git-1.7.11-preview20120620.exe is not accessible anymore for download, Are there any chance to rebuild git with this fix?
sschuberth commentedon Jul 10, 2012
@Siarhei-Yarkavy There currently is no released version which contains this fix. We are waiting for a few more days to see if more issues arise before we do another maintenance release.
the-Arioch commentedon Aug 2, 2012
Same on Git-1.7.11-preview20120710.exe
"few more days" ?
sschuberth commentedon Aug 2, 2012
The fix for this particular issue regarding the git wrapper is indeed included in Git-1.7.11-preview20120710.exe. If you still see Git returning an invalid exit code for some operation it is a different issue. Please create a new report in that case.