From: "Torsten Bögershausen" <tboegi@web•de>
To: Justin Tobler <jltobler@gmail•com>
Cc: Junio C Hamano <gitster@pobox•com>,
git@vger•kernel.org, karthik.188@gmail•com
Subject: Re: [RFC PATCH] diff: add option to report binary files in raw diffs
Date: Fri, 7 Nov 2025 09:30:15 +0100 [thread overview]
Message-ID: <20251107083015.GA18670@tb-raspi4> (raw)
In-Reply-To: <z5mkdl67vx47na5critwtyz7cacvhs6iixy46ia3svdoq7xui5@ckpfnjw3dkoq>
On Thu, Nov 06, 2025 at 03:42:49PM -0600, Justin Tobler wrote:
> On 25/11/05 12:04AM, Junio C Hamano wrote:
> > Justin Tobler <jltobler@gmail•com> writes:
> >
[snip]
> Currently the output in the next version will look like:
>
> :100644 100644 a1961526 e231acb1 binary=yy M foo
> :100644 100644 31eedd5c 402a70d7 binary=nn M bar
>
I think that is a good solutution ;-)
When I once developped the
git ls-files --eol option someone (Junio ?) convinced my to
use a TAB as a seperator.
In this case just before the filename:
git ls-file --eol | xxd
00000000: 692f 6c66 2020 2020 772f 6c66 2020 2020 i/lf w/lf
00000010: 6174 7472 2f20 2020 2020 2020 2020 2020 attr/
00000020: 2020 2020 2020 092e 6369 7272 7573 2e79 ..cirrus.y
^^
00000030: 6d6c 0a ml.
This makes the output both human readable and machine parsable:
All info is before the TAB here. (And may be parsed again in a second
round, if needed).
Thoughts ?
next prev parent reply other threads:[~2025-11-07 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 2:14 [RFC PATCH] diff: add option to report binary files in raw diffs Justin Tobler
2025-11-04 2:26 ` Junio C Hamano
2025-11-04 4:44 ` Junio C Hamano
2025-11-05 0:17 ` Justin Tobler
2025-11-05 8:04 ` Junio C Hamano
2025-11-06 21:42 ` Justin Tobler
2025-11-07 8:30 ` Torsten Bögershausen [this message]
2025-11-07 16:07 ` Junio C Hamano
2025-11-07 17:16 ` Justin Tobler
2025-11-07 17:26 ` Junio C Hamano
2025-11-05 12:14 ` Ben Knoble
2025-11-06 21:52 ` Justin Tobler
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=20251107083015.GA18670@tb-raspi4 \
--to=tboegi@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jltobler@gmail$(echo .)com \
--cc=karthik.188@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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