public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Eduard-Mihai Burtescu" <eddyb@lyken.rs>
To: "Ian Lance Taylor" <iant@google.com>
Cc: "Ian Lance Taylor" <ian@airs.com>,
	"Jakub Jelinek" <jakub@redhat.com>, "Jeff Law" <law@redhat.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Refactor rust-demangle to be independent of C++ demangling.
Date: Fri, 15 Nov 2019 21:00:00 -0000	[thread overview]
Message-ID: <408d4f54-3d3d-42ad-bab4-c46af66597f2@www.fastmail.com> (raw)
In-Reply-To: <CAKOQZ8wPwDJfqbT+KzpWQkh6jBV6fDZRNRdQgtJeWGmXsCQ6Wg@mail.gmail.com>

> This is OK.
> 
> Thanks.
> 
> Ian
>

Ping for someone to commit this (as mentioned before, I have no commit access).
I've tried pinging some people on IRC, but saw no response.

Approved version of the patch: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00647.html

Original email, containing the description: https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01591.html
(ignore the original patch, two changes had to be made before it was approved)

Thanks,
- Eddy B.

  reply	other threads:[~2019-11-15 20:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 18:24 Eduard-Mihai Burtescu
2019-10-22 18:48 ` Ian Lance Taylor via gcc-patches
2019-10-23 14:29   ` Eduard-Mihai Burtescu
2019-10-23 16:37     ` Alexander Monakov
2019-10-23 16:41       ` Segher Boessenkool
2019-10-23 17:19         ` Jakub Jelinek
2019-10-23 17:29           ` Segher Boessenkool
2019-10-23 17:37             ` Jakub Jelinek
2019-10-23 17:43               ` Segher Boessenkool
2019-10-25 12:46       ` Eduard-Mihai Burtescu
2019-10-30 16:56         ` Eduard-Mihai Burtescu
2019-11-08 17:02           ` Eduard-Mihai Burtescu
2019-11-08 17:44             ` Ian Lance Taylor via gcc-patches
2019-11-08 19:17               ` Eduard-Mihai Burtescu
2019-11-08 19:23                 ` Ian Lance Taylor via gcc-patches
2019-11-15 21:00                   ` Eduard-Mihai Burtescu [this message]
2019-11-16 15:39                 ` 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=408d4f54-3d3d-42ad-bab4-c46af66597f2@www.fastmail.com \
    --to=eddyb@lyken.rs \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=iant@google.com \
    --cc=jakub@redhat.com \
    --cc=law@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).