From: Joseph Myers <joseph@codesourcery.com>
To: Lewis Hyatt <lhyatt@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Patch to support extended characters in C/C++ identifiers
Date: Thu, 19 Sep 2019 19:57:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1909191956460.11875@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20190912203043.GB17354@ldh.local>
On Thu, 12 Sep 2019, Lewis Hyatt wrote:
> Attached is a single patch relative to current trunk that incorporates all of
> your feedback. I gzipped it like last time just in case the invalid UTF-8 in
> the tests presents a problem. The code changes are the same as before other
> than comments.
>
> The documentation is now updated... there were a couple other places that also
> seemed reasonable to me to update, hope it sounds OK.
Thanks, I've now committed this patch.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-09-19 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 22:16 Lewis Hyatt
2019-08-15 7:41 ` Jason Merrill
2019-08-15 12:51 ` Joseph Myers
2019-09-10 23:47 ` Joseph Myers
2019-09-11 14:32 ` Lewis Hyatt
2019-09-12 0:33 ` Joseph Myers
2019-09-12 20:30 ` Lewis Hyatt
2019-09-19 19:57 ` Joseph Myers [this message]
2019-09-19 20:08 ` 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.1909191956460.11875@digraph.polyomino.org.uk \
--to=joseph@codesourcery.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).