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

Re: Failed git commands and StGIT

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Jun 9, 2006, 21:05 UTC
Message-ID
<b0943d9e0606091405o79002a79id02e8fdd3936a345@mail.gmail.com>
In-Reply-To
<20060609183623.GJ11941@pasky.or.cz>
On 09/06/06, Petr Baudis <pasky@suse.cz> wrote:
Show 6 quoted lines
>   a user at #git just came with a problem with stg refresh - it turned
> out that he did not have his environment set up properly, but what is
> troublesome that stg refresh just said that "git-commit-tree failed" and
> did not show the actual error message - looking at the code, you
> probably want to keep fd 3 on the parent process' stderr, that is use
> open2, not open3.

I also found this annoying but I was too lazy to fix it. To not capture the stderr is easy (just change pass false as the 2nd argument to popen2.Popen3) but there is a duplicate of error messages from both GIT and StGIT. The other option is to add a '--verbose' option to most of the commands. I'll have a look at it this weekend.

Thanks.
-- 
Catalin
Previous: Petr BaudisNext: Petr Baudis
Message 2 of 3 in “Failed git commands and StGIT”
  1. Petr BaudisJun 9, 2006
  2. Catalin MarinasJun 9, 2006
  3. Petr BaudisJun 9, 2006

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.