From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [pushed] libstdc++: Tweak link to ABIcheck project
Date: Fri, 3 Feb 2023 19:51:22 +0000 [thread overview]
Message-ID: <CAH6eHdT2QGvxBCiSrWemPLnjLDop7RW3sqBqfPaMr6Z67=Ys5Q@mail.gmail.com> (raw)
In-Reply-To: <20230203192011.C853A33EBF@hamza.pair.com>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
On Fri, 3 Feb 2023, 19:20 Gerald Pfeifer wrote:
> libstdc++-v3/ChangeLog:
>
> * doc/xml/manual/abi.xml: Tweak link to ABIcheck project.
>
We should probably link to libabigail instead, or as well.
* doc/html/manual/abi.html: Regenerate.
> ---
> libstdc++-v3/doc/html/manual/abi.html | 2 +-
> libstdc++-v3/doc/xml/manual/abi.xml | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libstdc++-v3/doc/html/manual/abi.html
> b/libstdc++-v3/doc/html/manual/abi.html
> index 2781aeda30d..a9f7f04fa0c 100644
> --- a/libstdc++-v3/doc/html/manual/abi.html
> +++ b/libstdc++-v3/doc/html/manual/abi.html
> @@ -527,7 +527,7 @@ gcc test.c -g -O2 -L. -lone -ltwo
> /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.
> </p><p>
> <a class="link" href="http://gcc.gnu.org/PR19664" target="_top">19664:
> libstdc++ headers should have pop/push of the visibility around the
> declarations</a>
> </p></div><div class="bibliography"><div class="titlepage"><div><div><h3
> class="title"><a
> id="abi.biblio"></a>Bibliography</h3></div></div></div><div
> class="biblioentry"><a id="biblio.abicheck"></a><p>[biblio.abicheck] <span
> class="title"><em>
> - <a class="link" href="http://abicheck.sourceforge.net"
> target="_top">
> + <a class="link" href="https://abicheck.sourceforge.net"
> target="_top">
> ABIcheck
> </a>
> </em>. </span></p></div><div class="biblioentry"><a
> id="biblio.cxxabi"></a><p>[biblio.cxxabi] <span class="title"><em>
> diff --git a/libstdc++-v3/doc/xml/manual/abi.xml
> b/libstdc++-v3/doc/xml/manual/abi.xml
> index 3cca1fd3b38..3a3cbd3346c 100644
> --- a/libstdc++-v3/doc/xml/manual/abi.xml
> +++ b/libstdc++-v3/doc/xml/manual/abi.xml
> @@ -1130,7 +1130,7 @@ gcc test.c -g -O2 -L. -lone -ltwo
> /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.
> <biblioentry xml:id="biblio.abicheck">
> <title>
> <link xmlns:xlink="http://www.w3.org/1999/xlink"
> - xlink:href="http://abicheck.sourceforge.net">
> + xlink:href="https://abicheck.sourceforge.net">
> ABIcheck
> </link>
> </title>
> --
> 2.39.1
>
prev parent reply other threads:[~2023-02-03 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 19:20 Gerald Pfeifer
2023-02-03 19:51 ` Jonathan Wakely [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='CAH6eHdT2QGvxBCiSrWemPLnjLDop7RW3sqBqfPaMr6Z67=Ys5Q@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).