Re: git: 1181d23c283c - main_ -_=?utf-8?Q?textproc/riffdiff : update 3.4.1 =E2=86=92 3.4.2; update pager dependency =
- Reply: Adam Weinberger : "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 ="
- In reply to: Adam Weinberger : "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 ="
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 20 Oct 2025 14:35:56 UTC
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. ./danfe