2017-02-21 16:16, Mcnamara, John:
> From: Bruce Richardson
> >
> > 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
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, February 21, 2017 12:03 PM
> To: techbo...@dpdk.org
> Cc: dev@dpdk.org; Richardson, Bruce
> Subject: [dpdk-dev] [PATCH] doc: add details on requirements f
On Tue, Feb 21, 2017 at 03:12:32PM +0100, Thomas Monjalon wrote:
> 2017-02-21 12:02, Bruce Richardson:
> > +#. Once a patch has been acked by the relevant maintainer, reviewers may
> > still comment on it for a further
> > + two weeks. After that time, the patch should be merged into the
> > re
2017-02-21 12:02, Bruce Richardson:
> +#. Once a patch has been acked by the relevant maintainer, reviewers may
> still comment on it for a further
> + two weeks. After that time, the patch should be merged into the relevent
> git tree for the next release.
> + Additional notes and restrictio
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
5 matches
Mail list logo
