Author: luke1410
Date: Fri Dec 1 22:55:51 2017
New Revision: 1816926
URL: http://svn.apache.org/viewvc?rev=1816926&view=rev
Log:
* site/staging/docs/community-guide/mailing-lists.part.html: Replace two no
longer working/available links with replacements serving copies of the
original content.
Modified:
subversion/site/staging/docs/community-guide/mailing-lists.part.html
Modified: subversion/site/staging/docs/community-guide/mailing-lists.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/mailing-lists.part.html?rev=1816926&r1=1816925&r2=1816926&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/mailing-lists.part.html
(original)
+++ subversion/site/staging/docs/community-guide/mailing-lists.part.html Fri
Dec 1 22:55:51 2017
@@ -143,8 +143,8 @@ href="https://www.unicom.com/pw/reply-to
"Principle of Least Damage" and "Can't Find My Way Back Home"
sections. From time to time, someone posts asking why we don't set
the <tt>Reply-to</tt> header. Sometimes that person will mention <a
-href="http://www.metasystema.net/essays/reply-to.mhtml";
->http://www.metasystema.net/essays/reply-to.mhtml</a>, which
+href="http://marc.merlins.org/netrants/reply-to-useful.html";
+>http://marc.merlins.org/netrants/reply-to-useful.html</a>, which
gives arguments in favor of modifying the <tt>Reply-to</tt> field.
The list administrators are aware of both documents, and see that both
sides of the argument have merits, but in the end have chosen not to
@@ -227,7 +227,7 @@ not a major inconvenience even when done
advice on how to not flame people for their bad quoting habits, see <a
href="https://www.netmeister.org/news/learn2quote.html";
>https://www.netmeister.org/news/learn2quote.html</a> (Deutsch:
-<a href="http://learn.to/quote";>http://learn.to/quote</a>).</p>
+<a
href="http://www.afaik.de/usenet/faq/zitieren/download/zitieren-alles.html";>http://www.afaik.de/usenet/faq/zitieren/download/zitieren-alles.html</a>).</p>
</div> <!-- top-posting -->
