From: Jonathan Corbet <corbet@lwn.net>
To: Peter Oberparleiter <oberpar@linux.ibm.com>,
Wu XiangCheng <bobwxc@email.cn>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/gcov: Convert two tags to ref in dev-tools/gov.rst
Date: Thu, 08 Apr 2021 11:20:08 -0600 [thread overview]
Message-ID: <87r1jkzoaf.fsf@meer.lwn.net> (raw)
In-Reply-To: <75131ef2-2c6f-3fc4-8a79-bab0d0f7b633@linux.ibm.com>
Peter Oberparleiter <oberpar@linux.ibm.com> writes:
> On 03.04.2021 13:37, Wu XiangCheng wrote:
>> Htmldocs does not display the chapter number, convert the two manual
>> chapter number tags to ref tags.
>>
>> Signed-off-by: Wu XiangCheng <bobwxc@email.cn>
>
> Looks sane to me.
>
> Acked-by: Peter Oberparleiter <oberpar@linux.ibm.com>
>
> Unfortunately I don't know how documentation updates such as this one
> are typically handled...
I've applied it.
Thanks,
jon
prev parent reply other threads:[~2021-04-08 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 11:37 [PATCH] docs/gcov: Convert two tags to ref in dev-tools/gov.rst Wu XiangCheng
2021-04-07 14:16 ` Peter Oberparleiter
2021-04-08 17:20 ` Jonathan Corbet [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=87r1jkzoaf.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bobwxc@email.cn \
--cc=linux-doc@vger.kernel.org \
--cc=oberpar@linux.ibm.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).