linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: reply+AFA4ZONK73S45476YGDP3OOCIA2HHEVBNHHGBDYVM4@reply.github.com
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [mkerrisk/man-pages] Add note to state this is a very outdated mirror (PR #31)
Date: Mon, 10 Apr 2023 03:04:14 +0200	[thread overview]
Message-ID: <e6735982-9d5b-f63d-3bfb-164e3f6ce176@gmail.com> (raw)
In-Reply-To: <mkerrisk/man-pages/pull/31/c1501174582@github.com>


[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]

Hi,

On 4/9/23 19:20, Sebastian Carlos wrote:
> I agree. I would also like to note that the [website](https://man7.org/linux/man-pages/index.html) itself is outdated. It took a while for me to realize that it was outdated, so I would also appreciate a note on the [homepage](https://man7.org/linux/man-pages/index.html) too.

The official website of the Linux man-pages project is:
<https://www.kernel.org/doc/man-pages/>

I've updated most of it, basically by removing contents, and pointing
to the README and CONTRIBUTING files in the repository, which are the
main sources of information for the project at the moment.  I plan to
remove even more of the website, after adding a new MAINTAINING file
to the repo in the near future.

It may be that we add online HTML pages in the (not near) future, but
don't count on that for now; that would be a lot of work (at least to
provide the high-quality pages I'd like to provide).

Cheers,
Alex


-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

           reply	other threads:[~2023-04-10  1:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mkerrisk/man-pages/pull/31/c1501174582@github.com>]

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=e6735982-9d5b-f63d-3bfb-164e3f6ce176@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=reply+AFA4ZONK73S45476YGDP3OOCIA2HHEVBNHHGBDYVM4@reply.github.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 NNTP newsgroup(s).