From: "Shawn O. Pearce" <spearce@spearce.org>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: git@vger.kernel.org
Subject: Re: git-gui Error
Date: Tue, 13 Feb 2007 02:45:19 -0500 [thread overview]
Message-ID: <20070213074519.GA32687@spearce.org> (raw)
In-Reply-To: <20070213065616.GA4195@auto.tuwien.ac.at>
Martin Koegler <mkoegler@auto.tuwien.ac.at> wrote:
> Starting git-gui without any parameters display an error message instead
> of a usage message:
Starting it with no parameters (`git-gui` or `git gui`) should
work just fine. I do this all of the time on Mac OS X and Windows,
as it opens a commit window and keeps it running.
> Error in startup script: child process exited abnormally
> while executing
> "close $fd"
> (procedure "load_all_heads" line 11)
> invoked from within
> "load_all_heads"
> invoked from within
> "if {[is_enabled transport]} {
> load_all_remotes
> load_all_heads
>
> populate_branch_menu
> populate_fetch_menu
> populate_push_menu
> }"
According to this backtrace, we were trying to startup the UI
and load the branches, but:
git for-each-ref --format=%(refname) refs/heads
returned a non-zero exit code or something else with it went wrong.
Is this maybe a brand new repository? This is most certainly a bug
in git-gui, but I'd like to understand more about the environment
so I can track it down.
--
Shawn.
next prev parent reply other threads:[~2007-02-13 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 6:56 git-gui Error Martin Koegler
2007-02-13 7:45 ` Shawn O. Pearce [this message]
2007-02-13 21:53 ` Martin Koegler
2007-02-14 2:22 ` Shawn O. Pearce
2007-02-14 6:00 ` Shawn O. Pearce
2007-02-14 17:46 ` Martin Koegler
2007-02-15 2:40 ` Shawn O. Pearce
2007-02-15 6:07 ` Martin Koegler
2007-02-15 6:38 ` Shawn O. Pearce
2007-02-14 18:09 ` Martin Koegler
2007-02-15 4:07 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070213074519.GA32687@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.