From: Junio C Hamano <gitster@pobox.com>
To: Michael Montalbo <mmontalbo@gmail.com>
Cc: vincent@vinc17.net, git@vger.kernel.org, j6t@kdbg.org
Subject: Re: [BUG] "git diff --word-diff" gives a diff while they are only space changes
Date: Thu, 14 May 2026 16:37:39 +0900 [thread overview]
Message-ID: <xmqq8q9migqk.fsf@gitster.g> (raw)
In-Reply-To: <CAC2QwmKRyYfE+30Fh75gvAEmJjk8g-3k+G=RDiEJ-KGNExAEow@mail.gmail.com> (Michael Montalbo's message of "Tue, 12 May 2026 13:56:19 -0700")
Michael Montalbo <mmontalbo@gmail.com> writes:
> @@ -457,6 +457,11 @@ endif::git-diff[]
> +
> Note that despite the name of the first mode, color is used to
> highlight the changed parts in all modes if enabled.
> ++
> +Word diff works by finding word-level changes within each hunk of
> +the line-level diff. The line-level alignment determines which
> +changed lines are compared to each other, which can affect the
> +word-level output.
The added text may not say anything wrong, but I am not sure how it
helps the end user to know the way machinery works internally.
next prev parent reply other threads:[~2026-05-14 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 20:56 [BUG] "git diff --word-diff" gives a diff while they are only space changes Michael Montalbo
2026-05-12 21:17 ` Vincent Lefevre
2026-05-13 15:52 ` Michael Montalbo
2026-05-14 7:37 ` Junio C Hamano [this message]
2026-05-14 9:55 ` Vincent Lefevre
2026-05-15 13:22 ` Phillip Wood
-- strict thread matches above, loose matches on Subject: below --
2026-05-06 1:09 Vincent Lefevre
2026-05-08 12:48 ` Johannes Sixt
2026-05-08 21:39 ` Vincent Lefevre
2026-05-09 6:16 ` Johannes Sixt
2026-05-09 15:55 ` Vincent Lefevre
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=xmqq8q9migqk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=mmontalbo@gmail.com \
--cc=vincent@vinc17.net \
/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