From: "Torsten Bögershausen" <tboegi@web.de>
To: Alexander Rinass <alex@fournova.com>, Johannes Sixt <j6t@kdbg.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH] diff: run arguments through precompose_argv
Date: Wed, 6 Apr 2016 09:47:32 +0200 [thread overview]
Message-ID: <5704BF14.9060100@web.de> (raw)
In-Reply-To: <C52E38F0-B0F2-4769-A2C7-798D0CD99B47@fournova.com>
On 06.04.16 08:51, Alexander Rinass wrote:
>
>> On 05 Apr 2016, at 21:15, Johannes Sixt <j6t@kdbg.org> wrote:
>>
>> Am 05.04.2016 um 19:09 schrieb Junio C Hamano:
>>>> Thanks-to: Torsten Bögershausen <tboegi@web.de>
>>
>> I sense NFD disease: The combining diaresis should combine with the o, not the g. Here is a correct line to copy-and-paste if you like:
>>
>> Thanks-to: Torsten Bögershausen <tboegi@web.de>
>>
>> -- Hannes
>
> Thanks for reviewing and catching the NFD encoding error.
>
> I will send in a patch v2 with the correct NFC encoding.
>
> Would you also like me to alter the commit message as mentioned by Junio?
>
> I could rewrite the sentence:
>
> “As a result, no diff is displayed when feeding such a file path to the
> diff command.”
>
> into simply saying:
>
> “As a result, no diff is displayed.”
>
> However, I don't read the original message as it would imply that only
> file paths are affected by the precompose_argv call.
>
> Are there other suggestions on improving the commit message?
May be something like this, (but this is highly a personal taste question)
When running diff commands, file paths containing decomposed unicode code points
are not converted to precomposed unicode form under Mac OS X.
As a result, no diff is displayed.
Opposite to most builtin commands, the diff builtin is missing the
parse_options call, which internally runs arguments through the
precompose_argv call, which ensures all arguments are in precomposed
unicode form.
Fix the problem by adding a precompose_argv call to diff, diff-index, diff-files and diff-tree.
Signed-off-by: Alexander Rinass <alex@fournova.com>
Helped-By: Torsten Bögershausen <tboegi@web.de>
Helped-By: Junio C Hamano <gitster@pobox.com>
next prev parent reply other threads:[~2016-04-06 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 20:38 [PATCH] diff: run arguments through precompose_argv Alexander Rinass
2016-04-04 20:38 ` Alexander Rinass
2016-04-05 17:09 ` Junio C Hamano
2016-04-05 19:15 ` Johannes Sixt
2016-04-05 19:27 ` Torsten Bögershausen
2016-04-05 21:42 ` Junio C Hamano
2016-04-06 6:51 ` Alexander Rinass
2016-04-06 7:47 ` Torsten Bögershausen [this message]
2016-04-06 17:27 ` Junio C Hamano
2016-05-11 22:08 ` Junio C Hamano
2016-05-12 11:16 ` Alexander Rinass
2016-05-12 15:39 ` Junio C Hamano
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=5704BF14.9060100@web.de \
--to=tboegi@web.de \
--cc=alex@fournova.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.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).