From: Xi Ruoyao <xry111@xry111.site>
To: Jonathan Corbet <corbet@lwn.net>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: loongarch@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Update links of LoongArch ISA Vol1 and ELF psABI
Date: Sun, 04 Dec 2022 13:50:19 +0800 [thread overview]
Message-ID: <413486cc20a6f822362419d51f83dfd508b5021a.camel@xry111.site> (raw)
In-Reply-To: <87h6ycoist.fsf@meer.lwn.net>
On Sat, 2022-12-03 at 03:58 -0700, Jonathan Corbet wrote:
> Tiezhu Yang <yangtiezhu@loongson.cn> writes:
>
> > Tiezhu Yang (2):
> > docs/LoongArch: Update links of LoongArch ISA Vol1 and ELF psABI
> > docs/zh_CN/LoongArch: Update links of LoongArch ISA Vol1 and ELF psABI
> >
> > Documentation/loongarch/introduction.rst | 8 ++++----
> > Documentation/translations/zh_CN/loongarch/introduction.rst | 8 ++++----
> > 2 files changed, 8 insertions(+), 8 deletions(-)
>
> I've applied these - working links are better than broken ones. I
> assume, though, that the new URLs, too, will break the next time the
> manual is updated? Is there any chance Loongson could provide a stable
> URL for the current version of this manual instead?
Use a URL with tag name instead of "latest", like
https://github.com/loongson/LoongArch-Documentation/releases/download/2022.08.12/LoongArch-Vol1-v1.02-CN.pdf
It will still refer to an outdated doc if the doc is updated, but at
least it won't be broken.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-12-04 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 10:59 Tiezhu Yang
2022-12-01 10:59 ` [PATCH 1/2] docs/LoongArch: " Tiezhu Yang
2022-12-01 10:59 ` [PATCH 2/2] docs/zh_CN/LoongArch: " Tiezhu Yang
2022-12-03 10:58 ` [PATCH 0/2] " Jonathan Corbet
2022-12-04 5:50 ` Xi Ruoyao [this message]
2022-12-05 1:44 ` Tiezhu Yang
2022-12-04 8:32 ` Huacai Chen
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=413486cc20a6f822362419d51f83dfd508b5021a.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=kernel@xen0n.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®