From: Jonathan Wakely <jwakely@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Jason Merrill <jason@redhat.com>, gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2 RFC] c++: add color to function decl printing
Date: Fri, 14 Jan 2022 22:34:04 +0000 [thread overview]
Message-ID: <CACb0b4mRSo5B1NwB+A+TTLp07M3sj0WWLZRkq0oB3oCtS3_AYw@mail.gmail.com> (raw)
In-Reply-To: <09a59ea7dac1f605ba3545168c4ef57660212ffd.camel@redhat.com>
On Fri, 14 Jan 2022 at 21:49, David Malcolm wrote:
>
> Jonathan, did you try the v2 patch?
>
No, sorry.
next prev parent reply other threads:[~2022-01-14 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 5:39 [PATCH " Jason Merrill
2021-12-13 11:02 ` Jonathan Wakely
2021-12-13 14:58 ` [PATCH v2 " Jason Merrill
2022-01-14 21:49 ` David Malcolm
2022-01-14 22:34 ` Jonathan Wakely [this message]
2022-01-15 3:56 ` [PATCH v3 " Jason Merrill
2022-05-04 18:46 ` [PATCH v4] " Jason Merrill
2021-12-13 19:22 ` [PATCH RFC] " Martin Sebor
2021-12-13 23:00 ` Jonathan Wakely
2021-12-14 5:41 ` Jason Merrill
2021-12-14 18:02 ` Martin Sebor
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=CACb0b4mRSo5B1NwB+A+TTLp07M3sj0WWLZRkq0oB3oCtS3_AYw@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).