From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
sverre@rabbelier.nl, "Dirk Süsserott" <newsletter@dirk.my1.cc>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git gui: Possible to see which commands are executed?
Date: Thu, 22 May 2008 08:12:11 -0400 [thread overview]
Message-ID: <20080522121211.GL29038@spearce.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0805210930150.30431@racer>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Tue, 20 May 2008, Shawn O. Pearce wrote:
> >
> > Well, we do have GIT_TRACE, and git-gui --trace is sort of the
> > same idea. :-)
>
> Which brings me to the suggestion to reuse GIT_TRACE instead of adding
> an option...
Well... you may not want to see what GIT_TRACE causes, but you
do want to see what `git gui --trace` gives you. So I didn't
want to overload it.
--
Shawn.
next prev parent reply other threads:[~2008-05-22 12:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 12:03 git gui: Possible to see which commands are executed? Dirk Süsserott
2008-05-18 12:13 ` Miklos Vajna
2008-05-18 12:34 ` Dirk Süsserott
2008-05-19 2:21 ` Shawn O. Pearce
2008-05-20 19:03 ` Dirk Süsserott
2008-05-20 19:44 ` Shawn O. Pearce
2008-05-20 20:05 ` Sverre Rabbelier
2008-05-20 20:17 ` Shawn O. Pearce
2008-05-20 20:22 ` Sverre Rabbelier
2008-05-20 20:31 ` Shawn O. Pearce
2008-05-20 20:46 ` Sverre Rabbelier
2008-05-20 21:34 ` Junio C Hamano
2008-05-21 2:41 ` Shawn O. Pearce
2008-05-21 8:30 ` Johannes Schindelin
2008-05-21 9:27 ` Karl Hasselström
2008-05-22 12:12 ` Shawn O. Pearce [this message]
2008-05-22 20:55 ` Nigel Magnay
2008-05-22 23:05 ` Shawn O. Pearce
2008-05-20 20:12 ` Dirk Süsserott
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=20080522121211.GL29038@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newsletter@dirk.my1.cc \
--cc=sverre@rabbelier.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).