On Mon, 8 Jan 2024 at 01:22, Jonathan Wakely <jwak...@redhat.com> wrote: > > On Mon, 8 Jan 2024 at 01:13, Jonathan Wakely <jwak...@redhat.com> wrote: > > > > This V2 patch failed CI: > > https://patchwork.sourceware.org/project/gcc/patch/20240106151802.3356059-1-jwak...@redhat.com/ > > > > But that's because the UTF-8 characters in the patch got garbled in > > patchwork, so what got tested is not what I intend to push. I have > > Hmm, it's garbled in the public inbox too: > https://inbox.sourceware.org/libstdc++/20240108011829.3670492-1-jwak...@redhat.com/T/#u > See the additions to > libstdc++-v3/testsuite/std/format/functions/format.cc which should be > valid UTF-8. I wonder what my MUA is doing wrong. I'll have to > investigate.
It seems that git send-email doesn't specify UTF-8 when I hit Enter at this prompt: The following files are 8bit, but do not declare a Content-Transfer-Encoding. /tmp/OEXvA2gRe9/0001-libstdc-Add-Unicode-aware-width-estimation-for-std-f.patch Which 8bit encoding should I declare [UTF-8]? OK. Log says: ... Content-Type: text/plain Content-Transfer-Encoding: 8bit
