From: Matthias Lederhofer <matled@gmx.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] GIT_TRACE: show which built-in/external commands are executed
Date: Sun, 25 Jun 2006 18:10:20 +0200 [thread overview]
Message-ID: <E1FuXBk-0001SG-3n@moooo.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.63.0606251607090.29667@wbgn013.biozentrum.uni-wuerzburg.de>
> Hi,
>
> On Sun, 25 Jun 2006, Matthias Lederhofer wrote:
>
> > With the environment variable GIT_TRACE set git will show
> > - alias expansion
> > - built-in command execution
> > - external command execution
> > on stderr.
>
> Nice.
Thanks :)
> P.S.: Now we only have to convert all "git-" invocations in the scripts to
> "git " invocations so we can benefit from it. But that would mean two
> forks instead of one for the non-builtins. Hmm.
Why do we not use this policy:
git-* is guaranteed to be the normal command without any strange alias
expansion, default parameters or something else a script does not like
to be changed in the commands. So all scripts use git-*, this will
prevent a double exec. The path to git-* should be obtained using git
--exec-path in the beginnig.
git <command> is to be used by the user if he wants aliases, default
parameters and other fancy stuff.
Using this policy the user can always get the normal behaviour and it
is possible to shadown built-in commands etc.
next prev parent reply other threads:[~2006-06-25 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 10:57 [RFC] git --trace: trace command execution Matthias Lederhofer
2006-06-25 11:50 ` Junio C Hamano
2006-06-25 12:51 ` Matthias Lederhofer
2006-06-25 13:56 ` [PATCH] GIT_TRACE: show which built-in/external commands are executed Matthias Lederhofer
2006-06-25 14:11 ` Johannes Schindelin
2006-06-25 14:22 ` Petr Baudis
2006-06-25 16:10 ` Matthias Lederhofer [this message]
2006-06-25 23:30 ` Johannes Schindelin
2006-06-28 18:22 ` Matthias Lederhofer
2006-06-29 18:06 ` [RFC] git --trace: trace command execution Jakub Narebski
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=E1FuXBk-0001SG-3n@moooo.ath.cx \
--to=matled@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).