From: Paul Eggert <eggert@cs.ucla.edu>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: UTF-8 in glibc commit messages
Date: Tue, 13 Apr 2021 17:06:02 -0700 [thread overview]
Message-ID: <5e9119c5-afe3-d8f1-a732-8aa2f4955c3b@cs.ucla.edu> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104132016550.30343@digraph.polyomino.org.uk>
On 4/13/21 1:19 PM, Joseph Myers wrote:
> 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).
Thanks for the info. If I understand things correctly, commit messages
can spell contributors' names (using UTF-8), so long as the names can be
re-encoded into ISO-8859-15. At some point this restriction may become
more annoying than it currently is, but in the meantime I don't have an
urgent need to relax the checking.
next prev parent reply other threads:[~2021-04-14 0:06 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
2021-04-14 0:06 ` Paul Eggert [this message]
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=5e9119c5-afe3-d8f1-a732-8aa2f4955c3b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=joseph@codesourcery.com \
--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).