Re: [RFC] send-email: UTF-8 encoding in subject line
- From
D. Ben Knoble <ben.knoble@gmail.com>
- Date
- Feb 22, 2026, 14:53 UTC
- Message-ID
- <CALnO6CALy48cmpqSp7TMjkg0ZuuMwhw_hsvLU09yxp5MSEi=Wg@mail.gmail.com>
- In-Reply-To
- <xmqqldgmrom9.fsf@gitster.g>
On Sat, Feb 21, 2026 at 12:30 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 14 quoted lines
> > Shreyansh Paliwal <shreyanshpaliwalcmsmn@gmail.com> writes: > > >> Yeah, that was a bit confusing for me until I got used to it. Maybe > >> saying “[default: UTF-8]” would be a small and definite improvement? > > The current message can be mistaken, if the reader does not READ, if > it is asking a yes/no question, but with the "default" label, you > cannot imagine answering "yes", which is clearly not one of the > things in the same class as "UTF-8" that is given as the default, > which also serves as an example. > > This is indeed a clever hack (not hack on computer code but hack on > the mind of human who is reading the message).
Yep. I've seen it somewhere before; I thought it was from Portage's emerge in "ask" mode, but checking that doesn't seem to be the case.
-- D. Ben Knoble