From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: Question on textconv
Date: Tue, 4 Aug 2026 14:44:22 -0400 [thread overview]
Message-ID: <017e01dd2441$476839f0$d638add0$@nexbridge.com> (raw)
I experienced a change in how textconv works since about 2.50 and it is hard
to get past. I would appreciate advice:
When I define an external binary textconv, roughly like:
.gitattributes:
simple binary diff=enscr
.gitconfig
[diff "enscr"]
textconv = run -debug ../../enscribe-conv --verbose
binary = true
The supplied file going to the textconv program looks like
/tmp/git-blob-GFtIhK/simple
and is always empty regardless of the file contents.
When there is only one file named simple in the repository I can find it,
but otherwise
any ambiguity in the name makes textconv processing impractical. Somewhere
prior to this
I was supplied with the actual file in the working index instead of a temp
file.
Am I missing something?
Thanks,
Randall
next reply other threads:[~2026-08-04 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 18:44 rsbecker [this message]
2026-08-04 20:52 ` Question on textconv D. Ben Knoble
2026-08-04 21:45 ` rsbecker
2026-08-05 4:50 ` Jeff King
2026-08-05 11:36 ` D. Ben Knoble
2026-08-05 14:05 ` rsbecker
2026-08-06 4:10 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='017e01dd2441$476839f0$d638add0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox