From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Marek Polacek <polacek@redhat.com>, Gerald Pfeifer <gerald@pfeifer.com>
Subject: [PATCH] Remove broken URL from libstdc++ manual
Date: Thu, 05 Sep 2019 07:45:00 -0000 [thread overview]
Message-ID: <20190905074550.GA8816@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
The URL for the "What Are Allocators Good For?" article has been a
recurring source of problems. It moved from the C/C++ Users Journal
website to the Dr Dobbs site after CUJ shut down, and the original
domain changed hands, leaving old links pointing to nefarious sites.
Now the URL to the copy on drdobbs.com no longer works either and I
can't find a (legal) copy of the article online. The simplest solution
is to remove the URL.
* doc/xml/manual/allocator.xml: Remove URL for bibliography entry.
* doc/html/*: Regenerate.
Committed to trunk. I think I'll backport this too, so we don't keep a
non-working link in the docs on release branches.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1609 bytes --]
commit 45a605e970ea6db474e40c02aef6b18993fea05c
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Sep 5 08:40:35 2019 +0100
Remove broken URL from libstdc++ manual
The URL for the "What Are Allocators Good For?" article has been a
recurring source of problems. It moved from the C/C++ Users Journal
website to the Dr Dobbs site after CUJ shut down, and the original
domain changed hands, leaving old links pointing to nefarious sites.
Now the URL to the copy on drdobbs.com no longer works either and I
can't find a (legal) copy of the article online. The simplest solution
is to remove the URL.
* doc/xml/manual/allocator.xml: Remove URL for bibliography entry.
* doc/html/*: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/allocator.xml b/libstdc++-v3/doc/xml/manual/allocator.xml
index 0de1be9465a..922bc49091c 100644
--- a/libstdc++-v3/doc/xml/manual/allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/allocator.xml
@@ -482,12 +482,9 @@
</biblioentry>
<biblioentry>
- <title>
- <link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="http://www.drdobbs.com/the-standard-librarian-what-are-allocato/184403759">
+ <title>
The Standard Librarian: What Are Allocators Good For?
- </link>
- </title>
+ </title>
<author><personname><firstname>Matt</firstname><surname>Austern</surname></personname></author>
<publisher>
@@ -495,6 +492,7 @@
C/C++ Users Journal
</publishername>
</publisher>
+ <pubdate>2000-12</pubdate>
</biblioentry>
<biblioentry>
next reply other threads:[~2019-09-05 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 7:45 Jonathan Wakely [this message]
2019-10-07 18:55 ` Thomas Schwinge
2019-10-08 10:42 ` Jonathan Wakely
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=20190905074550.GA8816@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=libstdc++@gcc.gnu.org \
--cc=polacek@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).