Re: [PATCH] GIT_TRACE: show which built-in/external commands are executed

From: Matthias Lederhofer <matled@gmx.net>
Date: Jun 25, 2006, 16:10 UTC
Message-ID: <E1FuXBk-0001SG-3n@moooo.ath.cx>
In-Reply-To: <Pine.LNX.4.63.0606251607090.29667@wbgn013.biozentrum.uni-wuerzburg.de>

Show 11 quoted lines

> 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.