From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: web@dpdk.org
Cc: thomas.monjalon@6wind.com
Subject: [dpdk-web] [PATCH v2 2/2] inform where Message ID can be found
Date: Wed, 27 Jul 2016 15:34:35 +0200 [thread overview]
Message-ID: <1469626475-8996-2-git-send-email-nelio.laranjeiro@6wind.com> (raw)
In-Reply-To: <1469626475-8996-1-git-send-email-nelio.laranjeiro@6wind.com>
Some people does not have the possibility to display Email Headers in their
client, for them it is faster to get it from the patchwork.
Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
---
dev.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dev.html b/dev.html
index 9a01ab5..63cb9f0 100644
--- a/dev.html
+++ b/dev.html
@@ -90,6 +90,8 @@
--to dev@dpdk.org --cc <everybody discussing the patch></pre>
<p>Annotations take place after the 3 dashes and should explicit
what has changed since the previous version.
+ <p>The Message ID can be found in the email header of the previous patch or in its
+ <a href="http://dpdk.org/patch/14470">patchwork page</a>.
<p>In the case of a bug reported on the mailing list, the patch should be a reply to the bug report.
<p>An updated patchset should be a reply to the previous cover letter.
<p>When sending a patch serie, a cover letter may explain the global idea:
--
2.1.4
next prev parent reply other threads:[~2016-07-27 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 12:15 [dpdk-web] [PATCH 1/3] move up contribution guidelines link Nelio Laranjeiro
2016-07-27 12:15 ` [dpdk-web] [PATCH 2/3] add alternative to send another patch version Nelio Laranjeiro
2016-07-27 13:03 ` Thomas Monjalon
2016-07-27 13:25 ` Nélio Laranjeiro
2016-07-27 12:15 ` [dpdk-web] [PATCH 3/3] inform where Message ID can be found Nelio Laranjeiro
2016-07-27 13:22 ` Thomas Monjalon
2016-07-27 13:26 ` Nélio Laranjeiro
2016-07-27 13:01 ` [dpdk-web] [PATCH 1/3] move up contribution guidelines link Thomas Monjalon
2016-07-27 13:24 ` Nélio Laranjeiro
2016-07-27 13:34 ` [dpdk-web] [PATCH v2 1/2] " Nelio Laranjeiro
2016-07-27 13:34 ` Nelio Laranjeiro [this message]
2016-07-27 13:48 ` Thomas Monjalon
2016-07-27 13:51 ` Mcnamara, John
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=1469626475-8996-2-git-send-email-nelio.laranjeiro@6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@dpdk.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;
as well as URLs for NNTP newsgroup(s).