From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: git gui: Possible to see which commands are executed?
Date: Tue, 20 May 2008 15:44:03 -0400 [thread overview]
Message-ID: <20080520194403.GC29038@spearce.org> (raw)
In-Reply-To: <4833206E.1080300@dirk.my1.cc>
Dirk Ssserott <newsletter@dirk.my1.cc> wrote:
>
> thanks for your patch. Actually I had problems applying it and
> finally gave up. I'm using the msysGit package which seems quite
> similar to the cygwin package but not in all cases, apparently.
Well, msysGit is perhaps on an older version of git-gui. But
I had thought they were fairly current and that the section of
code the patch touches hasn't been modified in a while. Maybe
there was an issue with CRLF?
> However, you were right. The trace doesn't show the commands I
> would use on a regular basis (I couldn't stop you :-)).
> On the other hand it possibly helps to /understand/ (or at least
> /see/) what's going on under the hood.
>
> For that reason I'd greatly appreciate seeing your patch in some
> future version of Git. It doesn't do any harm, does it? People
> that don't like it can simply omit the '--trace' switch.
>
> Junio? The list?
Junio defers almost all git-gui things to me, as I am the current
maintainer of git-gui. You are right, it doesn't really hurt to
include it, and now that it is written, the hard part is already
done. I'll apply it to my main git-gui tree and ask Junio to
include it in a future version of Git.
--
Shawn.
next prev parent reply other threads:[~2008-05-20 19:45 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 [this message]
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
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=20080520194403.GC29038@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newsletter@dirk.my1.cc \
/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).