On 2018-08-27 06:13 PM, Stas Bekman wrote:
[...]
> I now know how get the filenames for "clean/smudge" filters. Can you
> please help with the same for "textconv". %f doesn't work - it gets
> stuck there waiting for stdin, the following seems to pass, but I'm not
> sure it's correct:
On a closer
On 2018-08-27 05:58 PM, Jeff King wrote:
[...]
>> 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
On Mon, Aug 27, 2018 at 05:22:13PM -0700, Stas Bekman wrote:
> 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:
>
On 2018-08-27 04:53 PM, Jeff King wrote:
> On Mon, Aug 27, 2018 at 04:23:34PM -0700, Stas Bekman wrote:
[...]
>> How can I get GIT_TRACE's run_command to show the arguments passed to
>> the filter? I looked at various other debug environment variables in
>> git's manual, but I don't see anything
On Mon, Aug 27, 2018 at 04:23:34PM -0700, Stas Bekman wrote:
> I'm debugging the workings of a configured git content filter
> (nbstripout) and I'm trying to get GIT_TRACE to show me the files it's
> operating on, but it doesn't. Consider:
>
> $ GIT_TRACE=1 git pull origin master
> [...] removed
Hello,
I'm debugging the workings of a configured git content filter
(nbstripout) and I'm trying to get GIT_TRACE to show me the files it's
operating on, but it doesn't. Consider:
$ GIT_TRACE=1 git pull origin master
[...] removed irrelevant sections of the output
16:49:28.846707
6 matches
Mail list logo