From: Integral <integral@archlinuxcn.org>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
ziyao@disroot.org, integral@archlinuxcn.org,
workflows@vger.kernel.org
Subject: A contradiction of "summary phrase" definition in process/submitting-patches.rst
Date: Mon, 31 Mar 2025 21:05:49 +0800 [thread overview]
Message-ID: <eb1abac9-d6d2-4dce-a5f6-d0702ceca103@archlinuxcn.org> (raw)
Hello,
I found a contradiction in process/submitting-patches.rst:
The canonical patch subject line is::
Subject: [PATCH 001/123] subsystem: summary phrase
The ``summary phrase`` may be prefixed by tags enclosed in square
brackets: "Subject: [PATCH <tag>...] <summary phrase>".
The former means "summary phrase" doesn't include "subsystem", while the
latter means "summary phrase" includes "subsystem".
So, which one is correct?
--
Integral
next reply other threads:[~2025-03-31 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 13:05 Integral [this message]
2025-03-31 13:23 ` Jonathan Corbet
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=eb1abac9-d6d2-4dce-a5f6-d0702ceca103@archlinuxcn.org \
--to=integral@archlinuxcn.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.org \
--cc=ziyao@disroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox