subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan <luke1...@posteo.de>
Subject Re: svn commit: r1816926 - /subversion/site/staging/docs/community-guide/mailing-lists.part.html
Date Fri, 01 Dec 2017 23:08:34 GMT
Giving some more details about this particular commit:

On 01/12/2017 23:55, luke1410@apache.org wrote:
> 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
The original link led me to a page stating: "It seems we can't find what
you're looking for".
I couldn't find an updated link on the original host (i.e.
metasystema.net) to that content, but was able to find what I believe is
the original content of this page at:
http://marc.merlins.org/netrants/reply-to-useful.html [1]

That page has a link to the parent/root page leading to
http://marc.merlins.org/netrants/listreplyto.html which explicitly
states that the link [1] is a local copy of the original link:
http://www.metasystema.net/essays/reply-to.mhtml. Hence, I have no doubt
that the content is accurate and replacing the link should be fine.
Any objections?

>  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 -->

Going to http://learn.to/quote tries to bring up some advertisement
popup (which my browser blocked and I didn't review). The page just
shows some php-errors:

/*"Warning*//: require(/include/afaik.de-header.inc.php3): failed to
open stream: No such file or directory in
//*/kunden/156453_33729/hosting/4833/afaik.de/usenet/faq/zitieren/zitieren.php3*//on
line //*2*//
////*Fatal error*//: require(): Failed opening required
'/include/afaik.de-header.inc.php3'
(include_path='.:/usr/local/lib/php') in
//*/kunden/156453_33729/hosting/4833/afaik.de/usenet/faq/zitieren/zitieren.php3*//on
line //*2"*/

I could find a replacement which claims to be a local copy of the
content which was available at the now broken linked page. Again I don't
have any doubt that this is a correct capture of the original content
(though it might not have been the latest version). Still, IMO this
seems to be a reasonable replacement for the broken link, or does
anybody think otherwise?

Regards,
Stefan
**


Mime
View raw message