From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao@amd.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
akiyks@gmail.com, ojeda@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bilbao@vt.edu, konstantin@linuxfoundation.org
Subject: Re: [PATCH v3 1/2] docs: Move rustdoc output, cross-reference it
Date: Wed, 07 Dec 2022 12:33:37 -0700 [thread overview]
Message-ID: <871qpbknzi.fsf@meer.lwn.net> (raw)
In-Reply-To: <5887a9cd-b48e-e2af-7639-3f9ff53fcd8a@amd.com>
Carlos Bilbao <carlos.bilbao@amd.com> writes:
> On 12/7/22 2:27 AM, Jani Nikula wrote:
>> Also, please don't use "here" as the link text.
>
> Why not?
Among other things, that makes things harder for people using screen
readers and other assistive technology.
Thanks,
jon
next prev parent reply other threads:[~2022-12-07 19:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 22:08 [PATCH] docs: Integrate rustdoc into Rust documentation Carlos Bilbao
2022-12-01 12:42 ` Miguel Ojeda
2022-12-01 20:40 ` Carlos Bilbao
2022-12-02 16:27 ` Miguel Ojeda
2022-12-02 16:30 ` Carlos Bilbao
2022-12-01 20:48 ` [PATCH v2] " Carlos Bilbao
2022-12-05 1:06 ` Akira Yokosawa
2022-12-05 16:08 ` Miguel Ojeda
2022-12-06 13:32 ` Akira Yokosawa
2022-12-06 15:02 ` Jonathan Corbet
2022-12-06 15:39 ` Miguel Ojeda
2022-12-05 16:36 ` Carlos Bilbao
2022-12-06 14:22 ` Akira Yokosawa
2022-12-06 14:55 ` Carlos Bilbao
2022-12-06 15:01 ` Carlos Bilbao
2022-12-06 15:31 ` [PATCH v3 0/2] " Carlos Bilbao
2022-12-06 15:31 ` [PATCH v3 1/2] docs: Move rustdoc output, cross-reference it Carlos Bilbao
2022-12-06 22:56 ` Akira Yokosawa
2022-12-07 8:27 ` Jani Nikula
2022-12-07 13:49 ` Carlos Bilbao
2022-12-07 14:15 ` Jani Nikula
2022-12-07 15:06 ` Carlos Bilbao
2022-12-07 19:33 ` Jonathan Corbet [this message]
2022-12-06 15:31 ` [PATCH v3 2/2] docs: Integrate rustdoc generation into htmldocs Carlos Bilbao
2022-12-06 23:11 ` Akira Yokosawa
2022-12-07 0:06 ` Randy Dunlap
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=871qpbknzi.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=jani.nikula@linux.intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.