public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>,
	"David Malcolm" <dmalcolm@redhat.com>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>
Cc: Joseph Myers <joseph@codesourcery.com>, Martin Sebor <msebor@gmail.com>
Subject: Re: [PATCH 0/3] Introduce internal_error_cont and exclude it from pot files
Date: Thu, 06 Apr 2017 16:44:00 -0000	[thread overview]
Message-ID: <408e109b-94ca-3e8d-8e3c-571fee8ca3b0@redhat.com> (raw)
In-Reply-To: <28c77f04-dbc1-1297-d7c3-f94700274a7e@suse.cz>

On 03/24/2017 03:29 AM, Martin Liška wrote:
> I would like to ping that. I'm not sure what's agreement after I read
> discussion in: https://gcc.gnu.org/ml/gcc/2017-03/msg00070.html
>
> Martin Sebor may know, CC'ing him.
Not sure if you're pinging the internal_error_cont stuff, or the ODR 
diagnostics changes.

WRT the ODR diagnostics, I'd say let's go with the C++17 style 
(all-lowercase with a hyphen).

If you've got a pointer to the internal_err_cont changes, please pass it 
along.

jeff

  parent reply	other threads:[~2017-04-06 16:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 13:54 Martin Liška
2017-03-15 18:33 ` David Malcolm
2017-03-20 13:10   ` Martin Liška
2017-03-24  9:39     ` Martin Liška
2017-03-24 16:22       ` Martin Sebor
2017-03-24 17:51         ` Jeff Law
2017-04-06 16:44       ` Jeff Law [this message]
2017-04-06 20:58         ` [wwwdocs, PATCH v2] C++ terminology: the One Definition Rule in diagnostics David Malcolm
2017-04-10  7:38           ` Gerald Pfeifer
2017-04-07 10:30         ` [PATCH 0/3] Introduce internal_error_cont and exclude it from pot files Martin Liška
2017-04-10 15:42           ` Jeff Law
2017-04-10 15:44             ` Richard Biener
2017-06-30 10:31               ` Martin Liška
2017-06-30 15:11                 ` Jeff Law

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=408e109b-94ca-3e8d-8e3c-571fee8ca3b0@redhat.com \
    --to=law@redhat.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=mliska@suse.cz \
    --cc=msebor@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).