Re: [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- May 10, 2013, 14:46 UTC
- Message-ID
- <CALkWK0k_ArM9EpY0S7=mbgFpHsoauZCr9e=ESX_CEA5-vRHrHQ@mail.gmail.com>
- In-Reply-To
- <7vmws2529j.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
Show 6 quoted lines
> Ramkumar Ramachandra <artagnon@gmail.com> writes: > >> A couple of tests execute 'git rebase' with GIT_TRACE set to 1, but >> this trace output is not used anywhere. > > Isn't it shown in "t4300-*.sh -v" output to help the debugger?
Um, but why the GIT_TRACE in just these two places? Can't I set GIT_TRACE=1 when executing the shell script if I really wanted that?