git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Return code in cmd (git describe)

From
MHManuela Hutter <manuelah@opera.com>
Date
Jul 31, 2012, 12:54 UTC
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:

Show 17 quoted lines
> 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

Previous: Konstantin Khomoutov
Message 3 of 3 in “Return code in cmd (git describe)”
  1. Manuela HutterJul 31, 2012
  2. Konstantin KhomoutovJul 31, 2012
  3. Manuela HutterJul 31, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.