From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: UTF-8 in glibc commit messages
Date: Tue, 13 Apr 2021 20:19:03 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2104132016550.30343@digraph.polyomino.org.uk> (raw)
In-Reply-To: <a5c371a5-48ea-1eb4-719a-0861d6797938@cs.ucla.edu>
On Tue, 13 Apr 2021, Paul Eggert wrote:
> Today I tried to install a glibc fix with some non-ASCII chars in the commit
> message, but sourceware.org rejected the fix with the diagnostic reproduced at
> the end of this email.
>
> I'm puzzled by the message, as I see that existing commit messages use UTF-8,
> e.g., 41f013cef24884604c303435dd1915be2ea5c0e0's commit message contains the
> phrase "Developer’s Manual" with the same curly apostrophe that my proposed
> commit used. Has something changed recently on sourceware.org to reject such
> commits?
At some point the hooks were updated from AdaCore upstream, though that's
a while ago now. hooks.no-rh-character-range-check is the relevant
setting in project.config (on ref refs/meta/config) to disable this check
(that setting was added to the hooks because I didn't think this check
would be appropriate for GCC).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-04-13 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 19:21 Paul Eggert
2021-04-13 20:19 ` Joseph Myers [this message]
2021-04-14 0:06 ` Paul Eggert
2021-04-14 15:01 ` Mike Frysinger
2021-04-14 17:41 ` DJ Delorie
2021-04-14 18:08 ` Paul Eggert
2021-04-14 18:16 ` Adhemerval Zanella
2021-04-14 18:24 ` Paul Eggert
2021-04-14 20:28 ` Mike Frysinger
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=alpine.DEB.2.22.394.2104132016550.30343@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).