On Tue, 31 Jul 2012 14:27:15 +0200, Konstantin Khomoutov
<flatw...@users.sourceforge.net> wrote:
On Tue, 31 Jul 2012 14:02:50 +0200
"Manuela Hutter" <manue...@opera.com> wrote:
we have some python scripts that are run from Visual Studio, and one
of them fails because of a wrong git return code when calling
'git describe --dirty'
[...]
Run from wingw, the return code is 0.
Run from cmd, the return code is 1.
Why?
Supposedly, when you run Git from cmd.exe, the git.cmd top-level script
(which wraps the git.exe binary) gets executed, and it's currently
affected by this bug [1] (fixed). When you run Git from Git bash, the
git.exe binary runs directly and hence the bug is not exposed.
1. https://github.com/msysgit/msysgit/issues/43
Great, thanks for the info!
/Manuela
--
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
