From: Joseph Myers <joseph@codesourcery.com>
To: Martin Sebor <msebor@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>,
Marek Polacek <polacek@redhat.com>,
Jason Merrill <jason@redhat.com>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] attribute copy, leaf, weakref and -Wmisisng-attributes (PR 88546)
Date: Fri, 04 Jan 2019 18:10:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1901041810050.4551@digraph.polyomino.org.uk> (raw)
In-Reply-To: <f452f954-a6f7-a3ab-a95e-869ca8d16963@gmail.com>
On Thu, 3 Jan 2019, Martin Sebor wrote:
> Ping: https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01616.html
This is OK (with the typo fix Jakub noted).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2019-01-04 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 6:01 Martin Sebor
2018-12-21 10:28 ` Jakub Jelinek
2018-12-21 16:05 ` Martin Sebor
2018-12-21 19:14 ` Joseph Myers
2018-12-22 0:16 ` Martin Sebor
2018-12-22 0:33 ` Jakub Jelinek
2018-12-22 2:13 ` Martin Sebor
2019-01-03 22:10 ` Martin Sebor
2019-01-03 22:10 ` Martin Sebor
2019-01-04 18:10 ` Joseph Myers [this message]
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.1901041810050.4551@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=msebor@gmail.com \
--cc=polacek@redhat.com \
--cc=rguenther@suse.de \
/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).