lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb1abac9-d6d2-4dce-a5f6-d0702ceca103@archlinuxcn.org>
Date: Mon, 31 Mar 2025 21:05:49 +0800
From: Integral <integral@...hlinuxcn.org>
To: corbet@....net
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 ziyao@...root.org, integral@...hlinuxcn.org, workflows@...r.kernel.org
Subject: A contradiction of "summary phrase" definition in
 process/submitting-patches.rst

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






Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ