From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/1] README: Use kernel.org URL
Date: Sun, 11 Feb 2024 19:25:14 +0100 [thread overview]
Message-ID: <ZckRCjwkUguQ2IsW@debian> (raw)
In-Reply-To: <20240123110424.169915-1-pvorel@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Hi Petr!
On Tue, Jan 23, 2024 at 12:04:24PM +0100, Petr Vorel wrote:
> https://kernel.org/pub/ is redirected to
> https://mirrors.edge.kernel.org/pub/, but it's better not rely on that
> and use the primary URL.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Thanks for the patch! I've applied it.
Have a lovely day,
Alex
> ---
> README | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/README b/README
> index 115e9f53a..974bd7564 100644
> --- a/README
> +++ b/README
> @@ -60,7 +60,7 @@ Files
>
> Versions
> Distribution
> - <https://mirrors.edge.kernel.org/pub/linux/docs/man-pages/>
> + <https://kernel.org/pub/linux/docs/man-pages/>
> <https://www.alejandro-colomar.es/share/dist/man-pages/>
>
> Git
> @@ -69,7 +69,7 @@ Versions
>
> Online man-pages
> PDF
> - <https://mirrors.edge.kernel.org/pub/linux/docs/man-pages/book/>
> + <https://kernel.org/pub/linux/docs/man-pages/book/>
> <https://www.alejandro-colomar.es/share/dist/man-pages/>
> HTML
> <https://man7.org/linux/man-pages/index.html>
> --
> 2.43.0
>
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-11 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 11:04 [PATCH 1/1] README: Use kernel.org URL Petr Vorel
2024-02-11 18:25 ` Alejandro Colomar [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=ZckRCjwkUguQ2IsW@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=pvorel@suse.cz \
/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).