Re: git: 1181d23c283c - main - =?utf-8?Q?textproc/riffdiff: update 3.4.1 =E2=86=92 3.4.2; update pager dependency =Q?textproc/riffdiff: update 3.4.1 =E2=86=92 3.4.2; update pager dependency =

From: Adam Weinberger <adamw_at_adamw.org>
Date: Mon, 20 Oct 2025 15:11:18 UTC
On Mon, Oct 20, 2025 at 10:35 AM Alexey Dokuchaev <danfe@freebsd.org> wrote:

> On Sat, Oct 18, 2025 at 06:30:31PM -0400, Adam Weinberger wrote:
> > Git handles unicode characters like the arrow you put in, but mlmmj
> > doesn't. I thought we'd decided a while back to stick with ASCII whenever
> > possible in commit messages? [...]
> >
> > Personally I'm a fan of UTF-8 in commit messages, but IIRC Bapt explained
> > a while back why mlmmj has to assume otherwise.
>
> While I'm strictly pro-ASCII for commit messages (and email), I recall that
> this particular bug is triggered by Git "subject" line (<cat>/<port>: ...)
> so as long as it is 7-bit, the rest can still be UTF-8 if one pleases,
> CMIW.


Thanks, Alexey! That is great info that I was completely unclear on. So
only the first line needs to be ASCII, and the rest can be as UTF-8-ey as
desired.

You're our most reliable curmudgeon (and I mean that in the most lovingly
way possible) so I'm somewhat reassured knowing that you are perfectly
happy in a 7-bit world :)


-- 
Adam Weinberger
adamw@adamw.org