Linux Documentation
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"elana.copperman@mobileye.com" <elana.copperman@mobileye.com>
Subject: Re: Removing the deprecated htmldocs for good?
Date: Fri, 10 Feb 2023 16:07:28 -0500	[thread overview]
Message-ID: <20230210210728.5zontxigmtqippta@nitro.local> (raw)
In-Reply-To: <87wnjm9iba.fsf@meer.lwn.net>

On Thu, Dec 30, 2021 at 09:19:21AM -0700, Jonathan Corbet wrote:
> > While scanning through the internet for kernel documentation, I
> > stumbled upon the old deprecated htmldocs under
> > https://www.kernel.org/doc/htmldocs/. I see that on
> > https://www.kernel.org/doc/, we already point out that 'htmldocs -
> > Kernel Documentation in docbook format (deprecated).' is deprecated.
> > If I am not mistaken, all the content from htmldocs has now been
> > transformed into .rst and has potentially evolved further and hence
> > all relevant information should also already be available somewhere in
> > https://www.kernel.org/doc/html/latest/.
> >
> > Is it now time to delete the content under
> > https://www.kernel.org/doc/htmldocs/ for good?
> 
> I think that time may have come, yes; perhaps just have it redirect to
> https://www.kernel.org/doc/html/latest/ instead?

I'm going through my backlog (of which I have lots) and I finally got around
to making this change. Requesting https://www.kernel.org/doc/htmldocs/ should
now send you to the archives site, and it's gone from the listing in
www.kernel.org/doc.

-K

      reply	other threads:[~2023-02-10 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 13:57 Removing the deprecated htmldocs for good? Lukas Bulwahn
2021-12-30 16:19 ` Jonathan Corbet
2023-02-10 21:07   ` Konstantin Ryabitsev [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=20230210210728.5zontxigmtqippta@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=elana.copperman@mobileye.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.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