public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Lewis Hyatt <lhyatt@gmail.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libcpp: Update cpp_wcwidth() to Unicode 14.0.0
Date: Fri, 24 Jun 2022 19:26:14 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2206241921530.77392@digraph.polyomino.org.uk> (raw)
In-Reply-To: <2bf3f5270abb8c42f035f33615157af8a81d2ca9.camel@redhat.com>

On Fri, 24 Jun 2022, David Malcolm via Gcc-patches wrote:

> > BTW, is this something simple enough I should just commit it without
> > bugging
> > the list for approval?
> 
> The patch seems reasonable to me, but Joseph seems to be the expert on
> i18n-related matters.
> 
> Joseph, do we have a policy on this?

I don't think we have a policy on Unicode updates specifically, but the 
general principle for updating files maintained outside GCC and copied 
verbatim into the GCC sources doesn't require prior approval.

(Note that Unicode data is also used to generate ucnid.h - data for 
Unicode characters in identifiers - we should probably also include 
DerivedNormalizationProps.txt and DerivedCoreProperties.txt in the 
checked-in Unicode data for that purpose.)

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2022-06-24 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 21:49 Lewis Hyatt
2022-06-24 18:25 ` David Malcolm
2022-06-24 19:26   ` Joseph Myers [this message]
2022-06-26 18:16     ` Lewis Hyatt

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.2206241921530.77392@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lhyatt@gmail.com \
    /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).