From: Ingo Schwarze <schwarze@usta.de>
To: Stephen Gregoratto <dev@sgregoratto.me>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Change man.voidlinux.eu -> man.voidlinux.org
Date: Fri, 29 Mar 2019 21:23:53 +0100 [thread overview]
Message-ID: <20190329202353.GB17904@athene.usta.de> (raw)
In-Reply-To: <20190326100858.2hduk467fqkw34z3@BlackBox>
Hi Stephen,
Stephen Gregoratto wrote on Tue, Mar 26, 2019 at 09:08:58PM +1100:
> Looking at mandoc.bsd.lv, the link to the Void Linux documentation index
> is to voidlinux.eu. Due to a registration mishap[1] the .eu TLD was
> snapped up by parties unknown, and all Void Linux resources are now
> located at voidlinux.org. Thus we should change the Void Linux link from
> man.voidlinux.eu to man.voidlinux.org. I'd patch it myself but the
> website does not seem to be available over public CVS.
>
> [1] https://voidlinux.org/news/2019/02/voidlinux-eu-gone.html
Ouch, such a mishap must be very inconvenient for the project.
I'm sorry that happened...
I updated the links from the mandoc site with the patch below;
grepping indicates there aren't any others, so hopefully i caught
them all. The links to Void in devhistory.html go to github.
There wasn't any need so far to ask people for help with the website,
so i don't invest the additional maintenance required to keep a
copy on anoncvs and cvsweb. I prefer that people look at the *code*
and make suggestions for that. :-)
Yours,
Ingo
P.S.
man.voidlinux.org uses an invalid security certificate.
The certificate expired on March 28, 2019, 5:51:28 PM GMT+1.
The current time is March 29, 2019, 9:21 PM.
Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Index: index.html
===================================================================
RCS file: /home/cvs/mandoc/www/index.html,v
retrieving revision 1.48
diff -u -p -r1.48 index.html
--- index.html 10 Mar 2019 10:35:32 -0000 1.48
+++ index.html 29 Mar 2019 20:04:17 -0000
@@ -143,7 +143,7 @@
<a href="https://man.openbsd.org/">OpenBSD</a> —
<a href="https://manpages.debian.org/">Debian</a> –
<a href="https://jlk.fjfi.cvut.cz/arch/manpages/">Arch</a> –
- <a href="https://man.voidlinux.eu/">Void</a> Linux</li>
+ <a href="https://man.voidlinux.org/">Void</a> Linux</li>
<li><a href="contact.html">Contact</a>
the <span class="nm">mandoc</span> developers,
for example for bug reports or for questions.</li>
Index: ports.html
===================================================================
RCS file: /home/cvs/mandoc/www/ports.html,v
retrieving revision 1.73
diff -u -p -r1.73 ports.html
--- ports.html 14 Mar 2019 13:23:26 -0000 1.73
+++ ports.html 29 Mar 2019 20:04:54 -0000
@@ -62,7 +62,7 @@
>aports/main/mdocml</a>
(1.14.3 port)<br>
Maintainers: Natanael Copa (ncopa@) and Daniel Sabogal</dd>
- <dt><a class="external" href="https://www.voidlinux.eu/">Void Linux</a>
+ <dt><a class="external" href="https://www.voidlinux.org/">Void Linux</a>
(default formatter since September 23, 2014;
default viewer since March 14, 2015;
a man-db package is also available)</dt>
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2019-03-29 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 10:08 Stephen Gregoratto
2019-03-29 20:23 ` Ingo Schwarze [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=20190329202353.GB17904@athene.usta.de \
--to=schwarze@usta.de \
--cc=dev@sgregoratto.me \
--cc=discuss@mandoc.bsd.lv \
/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 NNTP newsgroup(s).