From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>,
brouer@redhat.com
Subject: Re: [PATCH bpf-next v4] bpf: Fix some invalid links in bpf_devel_QA.rst
Date: Thu, 22 Apr 2021 19:07:50 +0200 [thread overview]
Message-ID: <20210422190750.7273292c@carbon> (raw)
In-Reply-To: <87pmymcofa.fsf@meer.lwn.net>
On Thu, 22 Apr 2021 09:46:33 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> Tiezhu Yang <yangtiezhu@loongson.cn> writes:
>
> > There exist some errors "404 Not Found" when I click the link
> > of "MAINTAINERS" [1], "samples/bpf/" [2] and "selftests" [3]
> > in the documentation "HOWTO interact with BPF subsystem" [4].
> >
> > As Jesper Dangaard Brouer said, the links work if you are browsing
> > the document via GitHub [5], so I think maybe it is better to use
> > the corresponding GitHub links to fix the issues in the kernel.org
> > official document [4], this change has no influence on GitHub and
> > looks like more clear.
>
> No, we really don't want to link to GitHub, that's what we have
> kernel.org for.
I fully agree.
I actually liked V3 better.
Back when I wrote the documentation with these links, the BPF doc was
not well integrated with the kernels doc-system. It is today, so it
makes sense to remove the links (that happens to work on GitHub) as you
did in V3.
Today BPF documentation is nicely organized via this link:
https://www.kernel.org/doc/html/latest/bpf/index.html
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2021-04-22 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 11:09 [PATCH bpf-next v4] bpf: Fix some invalid links in bpf_devel_QA.rst Tiezhu Yang
2021-04-22 15:46 ` Jonathan Corbet
2021-04-22 17:07 ` Jesper Dangaard Brouer [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=20210422190750.7273292c@carbon \
--to=brouer@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yangtiezhu@loongson.cn \
--cc=yhs@fb.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).