From: Manuela Hutter <manuelah@opera.com>
Date: Tue, 31 Jul 2012 12:54:40 GMT
Subject: Re: Return code in cmd (git describe)
Message-ID: <op.wia95es4t21y7h@id-c1003.oslo.osa>
In-Reply-To: <20120731162715.f1f01a825a7a0f74a2e3b412@domain007.com>

On Tue, 31 Jul 2012 14:27:15 +0200, Konstantin Khomoutov  
<flatworm@users.sourceforge.net> wrote:

> 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

Great, thanks for the info!
/Manuela