From: "Martin Liška" <mliska@suse.cz>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>,
"redi at gcc dot gnu.org" <redi@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: fix typo in acinclude.m4.
Date: Thu, 27 Jan 2022 15:35:05 +0100 [thread overview]
Message-ID: <ca41b9bf-e682-77d1-3a70-6cb667f71b66@suse.cz> (raw)
In-Reply-To: <CAH6eHdRPJiZMpjge3N=FYf3+GH0Gw8L00cLayRemsRETdh+2XA@mail.gmail.com>
On 1/27/22 15:25, Jonathan Wakely wrote:
> I have the same patch ready to push, but I'm away from the computer. Please push.
;) I've just pushed that to master.
Martin
prev parent reply other threads:[~2022-01-27 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 13:48 Martin Liška
2022-01-27 14:25 ` Jonathan Wakely
2022-01-27 14:35 ` Martin Liška [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=ca41b9bf-e682-77d1-3a70-6cb667f71b66@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=redi@gcc.gnu.org \
/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).