All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Akira Yokosawa <akiyks@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: Fix crossref to 'The canonical patch format'
Date: Thu, 28 Apr 2022 12:29:36 -0600	[thread overview]
Message-ID: <87bkwl6oz3.fsf@meer.lwn.net> (raw)
In-Reply-To: <64e105a5-50be-23f2-6cae-903a2ea98e18@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> The reference to `explicit_in_reply_to` is pointless as when the
> reference was added in the form of "#15" [1], Section 15) was "The
> canonical patch format".
> The reference of "#15" had not been properly updated in a couple of
> reorganizations during the plain-text SubmittingPatches era.
>
> Fix it by using `the_canonical_patch_format`.
>
> [1]: 2ae19acaa50a ("Documentation: Add "how to write a good patch summary" to SubmittingPatches")
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Fixes: 5903019b2a5e ("Documentation/SubmittingPatches: convert it to ReST markup")
> Fixes: 9b2c76777acc ("Documentation/SubmittingPatches: enrich the Sphinx output")
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: stable@vger.kernel.org # v4.9+
> ---
>  Documentation/process/submitting-patches.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied, thanks.

jon

      reply	other threads:[~2022-04-28 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  9:28 [PATCH] docs: submitting-patches: Fix crossref to 'The canonical patch format' Akira Yokosawa
2022-04-28 18:29 ` 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=87bkwl6oz3.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.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 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.