From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Costa Shulyupin <costa.shul@redhat.com>,
linux-doc@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: redirect from old arch to the new one
Date: Mon, 1 May 2023 00:20:21 +0100 [thread overview]
Message-ID: <20230501002021.44800b38@sal.lan> (raw)
In-Reply-To: <87r0s4b0pe.fsf@meer.lwn.net>
Em Fri, 28 Apr 2023 07:22:53 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab@kernel.org> writes:
>
> > Again, as this is something that only applies to websites hosting
> > documentation, IMO the best would be to have a separate file
> > ("conf_redirects.py") included on conf.py, that will be
> > auto-generated by a script that would receive, as input, the
> > initial Kernel version where redirects should be preserved.
>
> ...but again...I think we should observe an actual problem before we
> start adding any of this. Otherwise we'll just end up carrying a bunch
> of cruft indefinitely.
Agreed. Just saying that, if this is a real problem, a custom conf.py
would be the best approach.
Btw, if I'm not mistaken, our building system already allows it via:
make SPHINX_CONF=conf-redirects.py htmldocs
I suspect that it would be possible to add redirects extension and
its parameters on it, if someone ever needs it. No need to carry
such stuff at the Kernel upstream, as this would very likely limited
to some web sites that would be interested on keeping links to
old documentation's location.
Regards,
Mauro
prev parent reply other threads:[~2023-04-30 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 10:12 [PATCH] docs: redirect from old arch to the new one Costa Shulyupin
2023-04-27 13:27 ` Jonathan Corbet
[not found] ` <CADDUTFwGHytziCux07cXO0eYDUXYh3Scp=Qm96N+1wAX3ELDeg@mail.gmail.com>
2023-04-27 14:27 ` Jonathan Corbet
2023-04-27 14:38 ` Costa Shulyupin
2023-04-28 12:24 ` Mauro Carvalho Chehab
2023-04-28 13:22 ` Jonathan Corbet
2023-04-30 23:20 ` Mauro Carvalho Chehab [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=20230501002021.44800b38@sal.lan \
--to=mchehab@kernel.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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