From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Pedro Alves <pedro@palves.net>
Cc: David Malcolm <dmalcolm@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] Add gcc/make-unique.h
Date: Tue, 12 Jul 2022 19:59:55 +0100 [thread overview]
Message-ID: <CAH6eHdSzUez=nV8d=+s67ZSJVLXMe7-g-dUfczPp3=hkmo+s1Q@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdSyXzdQwtHDVMhYWYCQVtS0GpoSBycuGoC7_satKbPrbQ@mail.gmail.com>
On Tue, 12 Jul 2022 at 19:58, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> [OFFLIST]
Oops, sorry, reply-all fail. I meant to spare everybody any further
musing on this topic.
Really leaving the thread now!
next prev parent reply other threads:[~2022-07-12 19:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH6eHdSnGwtScODMveYha1S5WiDo6YsexN_pRqe9n4vq-Pmkig@mail.gmail.com>
2022-07-12 0:25 ` David Malcolm
2022-07-12 0:25 ` [PATCH 2/2] analyzer: use std::unique_ptr for pending_diagnostic/note David Malcolm
2022-07-12 6:48 ` [PATCH 1/2] Add gcc/make-unique.h Jonathan Wakely
2022-07-12 8:13 ` Jonathan Wakely
2022-10-26 20:40 ` [PATCH v3] " David Malcolm
2022-11-02 21:45 ` Jason Merrill
2022-07-12 13:23 ` [PATCH 1/2] " Pedro Alves
2022-07-12 13:45 ` Jonathan Wakely
2022-07-12 14:06 ` Pedro Alves
2022-07-12 15:14 ` Jonathan Wakely
2022-07-12 16:40 ` Pedro Alves
2022-07-12 18:22 ` Jonathan Wakely
2022-07-12 18:36 ` Pedro Alves
2022-07-12 18:41 ` Pedro Alves
2022-07-12 18:58 ` Jonathan Wakely
2022-07-12 18:59 ` Jonathan Wakely [this message]
2022-07-12 18:50 ` Jonathan Wakely
2022-07-12 18:56 ` Pedro Alves
2022-07-12 18:36 ` David Malcolm
2022-07-12 18:49 ` Pedro Alves
2022-10-21 16:01 David Malcolm
2022-10-25 23:00 ` David Malcolm
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='CAH6eHdSzUez=nV8d=+s67ZSJVLXMe7-g-dUfczPp3=hkmo+s1Q@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pedro@palves.net \
/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).