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

Re: [PATCH] t3701-add-interactive: tighten the check of trace output

From
Jeff King <peff@peff.net>
Date
Sep 10, 2018, 19:33 UTC
Message-ID
<20180910193333.GA24850@sigill.intra.peff.net>
In-Reply-To
<20180910191932.GB17224@localhost>
On Mon, Sep 10, 2018 at 09:19:32PM +0200, SZEDER Gábor wrote:
Show 7 quoted lines
> > I'd have thought that anybody
> > adding index-specific tracing would do it as GIT_TRACE_INDEX.
> 
> Depends on the purpose, I guess.  For tracing that is aimed to become
> part of in git, definitely.  However, for my own ad-hoc tracing used
> to try to make sense of some split-index corner cases, trace_printf()
> is perfect.

I don't mind it as a temporary debug thing, but it would be nice if it wasn't a temptation for people to include in their actual patches.

-Peff
Previous: SZEDER Gábor
Message 7 of 7 in “t3701-add-interactive: tighten the check of trace output”
  1. t3701-add-interactive: tighten the check of trace outputSZEDER Gábor, Sep 10, 2018
  2. Taylor BlauSep 10, 2018
  3. Taylor BlauSep 18, 2018
  4. Jeff KingSep 10, 2018
  5. Junio C HamanoSep 10, 2018
  6. SZEDER GáborSep 10, 2018
  7. Jeff KingSep 10, 2018

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.