public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
	Jeff Law <jeffreyalaw@gmail.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][V2] Add mold detection for libs.
Date: Mon, 31 Jan 2022 09:46:14 +0100	[thread overview]
Message-ID: <7d340111-4325-b9dd-4bcd-767f97a9e4d4@suse.cz> (raw)
In-Reply-To: <CAH6eHdTb4b_umBxB_w7rfh5Fa_F-YR1-T38x_JL6i1iGQOHWZA@mail.gmail.com>

On 1/28/22 23:01, Jonathan Wakely wrote:
> On Fri, 28 Jan 2022 at 18:17, Jeff Law wrote:
>>
>>
>>
>> On 1/24/2022 4:11 AM, Martin Liška wrote:
>>> On 1/21/22 17:54, Jonathan Wakely wrote:
>>>> Yes, OK (but please CC the libstdc++ list, not just me).
>>>
>>> Hello.
>>>
>>> Sorry for that. Anyway, I would like to install the extended version
>>> of the patch
>>> that touches all libraries.
>>>
>>> Ready to be installed?
>> It looks to me like Jon ack'd in his original reply.  "Yes, OK ..."
> 
> Yes the libstdc++ part is still OK. I can't approve the equivalent
> changes for the other libs.

Hi.

I understand Jeff's OK as an approval also for other libs.

I'm going to install it.

Martin

  reply	other threads:[~2022-01-31  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e3418294-e27a-cf67-3f31-f2d4873a8557@suse.cz>
2022-01-21 16:54 ` [PATCH] libstdc++: detect mold linker Jonathan Wakely
2022-01-24 11:11   ` [PATCH][V2] Add mold detection for libs Martin Liška
2022-01-28 18:17     ` Jeff Law
2022-01-28 22:01       ` Jonathan Wakely
2022-01-31  8:46         ` Martin Liška [this message]
2022-02-01 16:17           ` 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=7d340111-4325-b9dd-4bcd-767f97a9e4d4@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=libstdc++@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).