From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Date: Tue, 31 Jul 2012 12:27:15 GMT
Subject: Re: Return code in cmd (git describe)
Message-ID: <20120731162715.f1f01a825a7a0f74a2e3b412@domain007.com>
In-Reply-To: <op.wia7q0jqt21y7h@id-c1003.oslo.osa>

On Tue, 31 Jul 2012 14:02:50 +0200
"Manuela Hutter" <manuelah@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