From: Dodji Seketeli <dodji@seketeli.org>
To: Matthias Maennich <maennich@google.com>
Cc: libabigail@sourceware.org, gprocida@google.com,
kernel-team@android.com
Subject: Re: [PATCH 0/6] Drop C++03 compatibility layer from abg-cxx-compat.h
Date: Tue, 15 Dec 2020 09:47:29 +0100 [thread overview]
Message-ID: <86h7onmp5q.fsf@seketeli.org> (raw)
In-Reply-To: <20201214230855.1574934-1-maennich@google.com> (Matthias Maennich's message of "Mon, 14 Dec 2020 23:08:50 +0000")
Hello Matthias,
Matthias Maennich <maennich@google.com> a écrit:
> This drops the compatiblity layer and clears out the abg_compat namespace from
> definitions that are now provided via the standard. Subsequently, fix up the
> necessary imports and use std:: names instead.
>
> While abg-cxx-compat.h remains now empty, there are lined up patches that will
> make use it again. Hence leave it empty and the corresponding test untouched as
> well.
>
> Matthias Maennich (6):
> Drop C++03 compatibility layer
> Remove <functional> usages from abg_compat
> Remove <memory> usages from abg_compat
> Remove <unordered_map> usages from abg_compat
> Remove <unordered_set> usages from abg_compat
> Drop unneccessary includes of abg-cxx-compat.h
Applied the patchset to master, thanks!
Cheers!
--
Dodji
prev parent reply other threads:[~2020-12-15 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 23:08 Matthias Maennich
2020-12-14 23:08 ` [PATCH 1/6] Drop C++03 compatibility layer Matthias Maennich
2020-12-14 23:08 ` [PATCH 2/6] Remove <functional> usages from abg_compat Matthias Maennich
2020-12-14 23:08 ` [PATCH 3/6] Remove <memory> " Matthias Maennich
2020-12-14 23:08 ` [PATCH 4/6] Remove <unordered_map> " Matthias Maennich
2020-12-14 23:08 ` [PATCH 5/6] Remove <unordered_set> " Matthias Maennich
2020-12-14 23:08 ` [PATCH 6/6] Drop unneccessary includes of abg-cxx-compat.h Matthias Maennich
2020-12-15 8:47 ` Dodji Seketeli [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=86h7onmp5q.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.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).