From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add details on requirements for patch ack and merge
Date: Tue, 21 Feb 2017 16:16:16 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026D3C2C@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1487678567-13375-1-git-send-email-bruce.richardson@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, February 21, 2017 12:03 PM
> To: techboard@dpdk.org
> Cc: dev@dpdk.org; Richardson, Bruce <bruce.richardson@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: add details on requirements for patch ack
> and merge
>
> Add to the contributors guide the requirements and guidelines for getting
> patches acked and merged. It details at what point the review comments and
> the ack's need to be received in order to have a given patch merged into a
> release.
>
> These guidelines are as agreed by the DPDK technical board at the meeting
> held on 2017-02-15.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Minor nit. I'd prefer the first word of the bullet items to be capitalized
as a sentence. Apart from that:
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2017-02-21 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 12:02 Bruce Richardson
2017-02-21 14:12 ` Thomas Monjalon
2017-02-21 14:15 ` Bruce Richardson
2017-02-21 16:16 ` Mcnamara, John [this message]
2017-03-09 13:12 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE2026D3C2C@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@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).