Proper email threading is important for web ML archives
too...
How does the attached read to a native english speaker ?
Suggestions to put that elsewhere, or better phrasing...
Or maybe, as per akpm's tpp document suggest, this
introductory emails should be forbidden^wdiscouraged,
and the text properly dispatched in the apropriate
changelogs ?
P.S.: I'm not subscribed, and couldn't find a way to do a
proper reply to Arjan's message, so, sorry to break the
proposed rule myself...
--
Vincent Legoll
Add a suggestion to properly thread patch series
Discussion started in thread form 2006-11-30:
Re: [GFS2 & DLM] Guide to -nmw tree patches
---
commit dbdb1b56acc95508e720ba6fb04ebf8c4a5089fd
tree 6ef01b1ae85c24cb2643ef4c1de541fbfb9b583d
parent 0215ffb08ce99e2bb59eca114a99499a4d06e704
author Vincent Legoll <[email protected]> Fri, 01 Dec 2006 00:03:46 +0100
committer Vincent Legoll <[email protected]> Fri, 01 Dec 2006 00:03:46 +0100
Documentation/SubmittingPatches | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 302d148..00f96c7 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -116,6 +116,9 @@ in your patch description.
If you cannot condense your patch set into a smaller set of patches,
then only post say 15 or so at a time and wait for review and integration.
+If your patch set is not trivial, and you want to introduce the series
+with a presentation email, please post all the patches as a reply to that
+introduction, so that the whole email set is properly threaded.
4) Select e-mail destination.
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]