public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Legoll <legoll@online.fr>
To: linux-kernel@vger.kernel.org
Cc: arjan@infradead.org, swhiteho@redhat.com,
	Vincent Legoll <vincent.legoll@gmail.com>
Subject: Re: [GFS2 & DLM] Guide to -nmw tree patches
Date: Fri, 01 Dec 2006 00:58:18 +0100	[thread overview]
Message-ID: <456F701A.8090102@online.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

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


[-- Attachment #2: submittingpatches.gitpatch --]
[-- Type: text/plain, Size: 1175 bytes --]

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 <vincent.legoll@gmail.com> Fri, 01 Dec 2006 00:03:46 +0100
committer Vincent Legoll <vincent.legoll@gmail.com> 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.

             reply	other threads:[~2006-11-30 23:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 23:58 Vincent Legoll [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-30 12:12 [GFS2 & DLM] Guide to -nmw tree patches Steven Whitehouse
2006-11-30 12:21 ` Arjan van de Ven
2006-11-30 12:31   ` Steven Whitehouse
2006-12-01 18:38   ` Russell Cattelan

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=456F701A.8090102@online.fr \
    --to=legoll@online.fr \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    --cc=vincent.legoll@gmail.com \
    /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