Re: GIT_TRACE doesn't show content filter files it's operating on

From: Jeff King <peff@peff.net>
Date: Aug 28, 2018, 00:58 UTC
Message-ID: <20180828005810.GA18659@sigill.intra.peff.net>
In-Reply-To: <28045b26-4822-b00c-30f3-1076d2e49d1f@stason.org>

On Mon, Aug 27, 2018 at 05:22:13PM -0700, Stas Bekman wrote:

Show 5 quoted lines

> Your suggestions do the trick, Jeff. Thank you.
> 
> 1. To benefit others who might be looking for something similar may I
> post your suggestions as an answer to:
> <https://stackoverflow.com/questions/51995773/getting-git-to-show-specific-filenames-it-is-running-content-filters-on>?

Great, thanks.

Show 6 quoted lines

> 2. Is there no way to get git to do the filename reporting as a normal
> GIT_TRACE behavior? I don't know anything about its internal workings,
> but it surely must knows which file it operates on when it opens it and
> sends its data as stdin to the content filter. It makes the debugging so
> much easier when one can see what files are being worked on. So perhaps
> this utility can be made available to all not just as a hack/workaround.

No, because GIT_TRACE itself only reports on the execution of commands and sub-processes. There are other GIT_TRACE_* variables for various subsystems, but AFAIK nobody has instrumented the smudge/clean filter code. IMHO it would be reasonable to have a GIT_TRACE_CONVERT that covered convert.c (so these filters, but also newline conversion, etc).

-Peff