Re: [PATCH] GIT_TRACE: show which built-in/external commands are executed
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jun 25, 2006, 23:30 UTC
- Message-ID
- <Pine.LNX.4.63.0606260129410.29667@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <E1FuXBk-0001SG-3n@moooo.ath.cx>
Hi,
On Sun, 25 Jun 2006, Matthias Lederhofer wrote:
Show 11 quoted lines
> > 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.
That still leaves my problem: GIT_TRACE=1 on scripts is incomplete.
Ciao, Dscho