* Failed git commands and StGIT
@ 2006-06-09 18:36 Petr Baudis
2006-06-09 21:05 ` Catalin Marinas
0 siblings, 1 reply; 3+ messages in thread
From: Petr Baudis @ 2006-06-09 18:36 UTC (permalink / raw)
To: catalin.marinas; +Cc: git
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Failed git commands and StGIT
2006-06-09 18:36 Failed git commands and StGIT Petr Baudis
@ 2006-06-09 21:05 ` Catalin Marinas
2006-06-09 21:25 ` Petr Baudis
0 siblings, 1 reply; 3+ messages in thread
From: Catalin Marinas @ 2006-06-09 21:05 UTC (permalink / raw)
To: Petr Baudis; +Cc: git
On 09/06/06, Petr Baudis <pasky@suse.cz> wrote:
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Failed git commands and StGIT
2006-06-09 21:05 ` Catalin Marinas
@ 2006-06-09 21:25 ` Petr Baudis
0 siblings, 0 replies; 3+ messages in thread
From: Petr Baudis @ 2006-06-09 21:25 UTC (permalink / raw)
To: Catalin Marinas; +Cc: git
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...
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-06-09 21:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-09 18:36 Failed git commands and StGIT Petr Baudis
2006-06-09 21:05 ` Catalin Marinas
2006-06-09 21:25 ` Petr Baudis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox