From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>, linux-doc@vger.kernel.org
Cc: Costa Shulyupin <costa.shul@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: redirect from old arch to the new one
Date: Thu, 27 Apr 2023 07:27:01 -0600 [thread overview]
Message-ID: <87ildhfobe.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230427101241.1273752-1-costa.shul@redhat.com>
Costa Shulyupin <costa.shul@redhat.com> writes:
> Due to a recent reorganization of 'CPU Architectures', the links to
> the documentation from external resources were rendered invalid.
> This is a common challenge when attempting to make changes
> while maintaining backward compatibility. To address this issue,
> a commit has been made which uses sphinx extension to seamlessly
> redirect users from the old location of the page to the new one.
>
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> ---
> Documentation/conf.py | 8 +++++++-
> Documentation/sphinx/requirements.txt | 1 +
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 37314afd1ac8..514bfe6a8166 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -55,7 +55,13 @@ needs_sphinx = '1.7'
> extensions = ['kerneldoc', 'rstFlatTable', 'kernel_include',
> 'kfigure', 'sphinx.ext.ifconfig', 'automarkup',
> 'maintainers_include', 'sphinx.ext.autosectionlabel',
> - 'kernel_abi', 'kernel_feat']
> + 'kernel_abi', 'kernel_feat',
> + 'sphinx_reredirects',
> +]
> +
> +redirects = {
> + "arch.html": "arch/index.html",
> +}
I am not generally opposed to doing this, but:
- It only solves part of the problem; links directly into (say) the x86
docs will still break.
- Is there really a problem? Are there to-be-broken links out there
that you can point to?
Thanks,
jon
next prev parent reply other threads:[~2023-04-27 13:27 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 [this message]
[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
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=87ildhfobe.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).