From: Lorenzo Pegorari <lorenzo.pegorari2002@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #07)
Date: Thu, 22 Jan 2026 01:59:06 +0100 [thread overview]
Message-ID: <aXF2WtWh5RV3wGgk@lorenzo-VM> (raw)
In-Reply-To: <xmqq5x8uu6yk.fsf@gitster.g>
Hey Junio
> * lp/diff-stat-utf8-display-width-fix (2026-01-15) 2 commits
> - t4073: add test for diffstat paths length when containing UTF-8 chars
> - diff: improve scaling of filenames in diffstat to handle UTF-8 chars
>
> The computation of column width made by "git diff --stat" was
> confused when pathnames contain non-ASCII characters.
>
> Will merge to 'next'?
> source: <cover.1768520441.git.lorenzo.pegorari2002@gmail.com>
I would say yes, if you agree. The patch seems fine to me, and I
wouldn't change it in any way.
Also, thank you so much for your guidance and for dealing with my many
mistakes. Now I feel much more comfortable working with a mailing list,
so the number of my mistakes should decrease sharply (I hope :-)).
Lorenzo
prev parent reply other threads:[~2026-01-22 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 19:00 What's cooking in git.git (Jan 2026, #07) Junio C Hamano
2026-01-21 21:03 ` Lucas Seiki Oshiro
2026-01-21 21:08 ` Junio C Hamano
2026-01-22 0:59 ` Lorenzo Pegorari [this message]
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=aXF2WtWh5RV3wGgk@lorenzo-VM \
--to=lorenzo.pegorari2002@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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