From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Thorsten Otto" <admin@tho-otto.de>
Cc: git@vger.kernel.org
Subject: Re: "git diff" does not show a diff for newly added, binary files
Date: Tue, 04 Apr 2023 13:29:25 +0200 [thread overview]
Message-ID: <fa47135f-48f7-4cf9-b239-ebdd5b9872d0@app.fastmail.com> (raw)
In-Reply-To: <1997583.yJf2vTnlun@earendil>
On Tue, Apr 4, 2023, at 13:23, Thorsten Otto wrote:
> How can that be done? I mean, git detects that file to be binary. I certainly
> don't want to treat it as text, and then dump binary data to the terminal when
> they differ ;)
I used something like this when I last needed to diff binary files: https://superuser.com/a/706286/259670
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2023-04-04 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 9:58 "git diff" does not show a diff for newly added, binary files Thorsten Otto
2023-04-04 10:17 ` Kristoffer Haugsbakk
2023-04-04 10:39 ` Thorsten Otto
2023-04-04 10:45 ` Kristoffer Haugsbakk
2023-04-04 11:23 ` Thorsten Otto
2023-04-04 11:29 ` Kristoffer Haugsbakk [this message]
2023-04-04 15:36 ` Jeff King
2023-04-04 15:42 ` Junio C Hamano
2023-04-04 15:37 ` Junio C Hamano
2023-04-04 15:39 ` 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=fa47135f-48f7-4cf9-b239-ebdd5b9872d0@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=admin@tho-otto.de \
--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;
as well as URLs for NNTP newsgroup(s).