* [PATCH] SubmittingPatches: make Subject examples match the de facto standard
@ 2015-09-20 12:11 Alex Henrie
2015-09-24 21:57 ` Jonathan Corbet
0 siblings, 1 reply; 3+ messages in thread
From: Alex Henrie @ 2015-09-20 12:11 UTC (permalink / raw)
To: corbet, linux-doc, linux-kernel; +Cc: Alex Henrie
The examples should better match what kernel developers actually expect,
so that they set a good example both for this project and for other
projects with similar development processes.
Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
---
Documentation/SubmittingPatches | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index fd89b04..4710e4a 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -659,8 +659,8 @@ succinct and descriptive, but that is what a well-written summary
should do.
The "summary phrase" may be prefixed by tags enclosed in square
-brackets: "Subject: [PATCH tag] <summary phrase>". The tags are not
-considered part of the summary phrase, but describe how the patch
+brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
+not considered part of the summary phrase, but describe how the patch
should be treated. Common tags might include a version descriptor if
the multiple versions of the patch have been sent out in response to
comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
@@ -672,8 +672,8 @@ the patch series.
A couple of example Subjects:
- Subject: [patch 2/5] ext2: improve scalability of bitmap searching
- Subject: [PATCHv2 001/207] x86: fix eflags tracking
+ Subject: [PATCH 2/5] ext2: improve scalability of bitmap searching
+ Subject: [PATCH v2 01/27] x86: fix eflags tracking
The "from" line must be the very first line in the message body,
and has the form:
--
2.5.2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] SubmittingPatches: make Subject examples match the de facto standard
2015-09-20 12:11 [PATCH] SubmittingPatches: make Subject examples match the de facto standard Alex Henrie
@ 2015-09-24 21:57 ` Jonathan Corbet
2015-09-24 23:09 ` Alex Henrie
0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Corbet @ 2015-09-24 21:57 UTC (permalink / raw)
To: Alex Henrie; +Cc: linux-doc, linux-kernel
On Sun, 20 Sep 2015 14:11:19 +0200
Alex Henrie <alexhenrie24@gmail.com> wrote:
> The examples should better match what kernel developers actually expect,
> so that they set a good example both for this project and for other
> projects with similar development processes.
Applied to the docs tree, thanks.
jon
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] SubmittingPatches: make Subject examples match the de facto standard
2015-09-24 21:57 ` Jonathan Corbet
@ 2015-09-24 23:09 ` Alex Henrie
0 siblings, 0 replies; 3+ messages in thread
From: Alex Henrie @ 2015-09-24 23:09 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-doc, LKML
2015-09-24 23:57 GMT+02:00 Jonathan Corbet <corbet@lwn.net>:
> On Sun, 20 Sep 2015 14:11:19 +0200
> Alex Henrie <alexhenrie24@gmail.com> wrote:
>
>> The examples should better match what kernel developers actually expect,
>> so that they set a good example both for this project and for other
>> projects with similar development processes.
>
> Applied to the docs tree, thanks.
Thank you! The little things do matter ;-)
-Alex
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-09-24 23:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-20 12:11 [PATCH] SubmittingPatches: make Subject examples match the de facto standard Alex Henrie
2015-09-24 21:57 ` Jonathan Corbet
2015-09-24 23:09 ` Alex Henrie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®