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] Multibyte awareness for diagnostics (PR 49973)
Date: Tue, 19 Nov 2019 18:40:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1911191809570.7856@digraph.polyomino.org.uk> (raw)
In-Reply-To: <8a30a5a30078714f399822b0513b070af59c3e88.camel@redhat.com>
On Tue, 19 Nov 2019, David Malcolm wrote:
> If we're going with this approach, and redistributing those unicode data
> files as part of our repo and tarballs, do we need some kind of
> copyright/license statement that spells out the situation? What does
> glibc do for this?
glibc includes the files in localedata/unicode-gen/ directory.
My inclination is that we should include them in the GCC sources, but
there were concerns about doing so when I asked about that issue when last
updating the data used for warnings about normalization of UCNs in
identifiers (which I should probably update again - given the work I did
last time, this time it should just be a regeneration with newer input
files) <https://gcc.gnu.org/ml/gcc-patches/2013-11/msg01932.html>.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-11-19 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 20:16 Lewis Hyatt
2019-09-26 20:47 ` Joseph Myers
2019-09-26 20:51 ` Lewis Hyatt
2019-09-27 20:42 ` Lewis Hyatt
2019-10-18 13:59 ` Lewis Hyatt
2019-11-19 17:38 ` David Malcolm
2019-11-19 18:40 ` Joseph Myers [this message]
2019-11-19 22:33 ` Joseph Myers
2019-11-20 16:31 ` Lewis Hyatt
2019-11-20 16:39 ` Lewis Hyatt
2019-11-22 3:24 ` David Malcolm
2019-11-22 11:06 ` David Malcolm
2019-11-26 17:12 ` Lewis Hyatt
2019-12-06 15:54 ` David Malcolm
2019-12-06 20:31 ` Lewis Hyatt
2019-12-09 20:12 ` David Malcolm
2019-12-09 23:00 ` 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.21.1911191809570.7856@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).