threads / discuss / 4445

Failed git commands and StGIT

Subject: Failed git commands and StGIT

## tl;dr

3 messages between Jun 9, 2006 and Jun 9, 2006.

replies: 2people: 2as markdown or json

Petr Baudis· Jun 9, 2006, 18:36 UTC · lore

Hi,

  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.

  The user has used StGIT 0.9.

  Thanks,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.

Catalin Marinas· Jun 9, 2006, 21:05 UTC · re: Petr Baudis · lore

Re: Failed git commands and StGIT

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

Petr Baudis· Jun 9, 2006, 21:25 UTC · re: Catalin Marinas · lore

Re: Failed git commands and StGIT

Dear diary, on Fri, Jun 09, 2006 at 11:05:47PM CEST, I got a letter where Catalin Marinas <catalin.marinas@gmail.com> said that...

Show 5 quoted lines

> 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.

  I don't think this is actually an issue. I'd actually prefer the
behaviour of NOT having to add a '--verbose' option to a stgit command
to see the full error output.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.