git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE

From
Junio C Hamano <gitster@pobox.com>
Date
May 10, 2013, 15:42 UTC
Message-ID
<7vr4he3kpz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CALkWK0k_ArM9EpY0S7=mbgFpHsoauZCr9e=ESX_CEA5-vRHrHQ@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 10 quoted lines
> Junio C Hamano wrote:
>> 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?

Perhaps because this is a test about "rebase" and a typical debugger does not want to trace other "git" things while debugging this?

Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 11 of 21 in “Trivial cleanups to t3400 (rebase)”
  1. 0/4 Trivial cleanups to t3400 (rebase)Ramkumar Ramachandra, May 10, 2013
  2. 1/4 t3400 (rebase): don't set GIT_AUTHOR_{NAME,EMAIL}Ramkumar Ramachandra, May 10, 2013
  3. Eric SunshineMay 10, 2013
  4. Ramkumar RamachandraMay 10, 2013
  5. Junio C HamanoMay 10, 2013
  6. 2/4 t3400 (rebase): downcase a couple of test titlesRamkumar Ramachandra, May 10, 2013
  7. 3/4 t3400 (rebase): move lone statement into a testRamkumar Ramachandra, May 10, 2013
  8. 4/4 t4300 (rebase): don't unnecessarily set GIT_TRACERamkumar Ramachandra, May 10, 2013
  9. Junio C HamanoMay 10, 2013
  10. Ramkumar RamachandraMay 10, 2013
  11. Junio C HamanoMay 10, 2013
  12. Ramkumar RamachandraMay 10, 2013
  13. Junio C HamanoMay 10, 2013
  14. Ramkumar RamachandraMay 10, 2013
  15. Ramkumar RamachandraMay 10, 2013
  16. Jonathan NiederMay 10, 2013
  17. Ramkumar RamachandraMay 10, 2013
  18. Jonathan NiederMay 10, 2013
  19. Junio C HamanoMay 10, 2013
  20. Ramkumar RamachandraMay 11, 2013
  21. Jonathan NiederMay 13, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.