From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: [PATCH] doc: add details on requirements for patch ack and merge
Date: Tue, 21 Feb 2017 15:12:32 +0100 [thread overview]
Message-ID: <5210332.Rcp5tEyIor@xps13> (raw)
In-Reply-To: <1487678567-13375-1-git-send-email-bruce.richardson@intel.com>
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 restrictions:
> +
> + * patches should be acked by a maintainer at least two days before the release merge
> + deadline, in order to make that release.
> + * for patches acked with less than two weeks to go to the merge deadline, all additional
> + comments should be made no later than two days before the merge deadline.
Do we need a drawing to illustrate the deadlines? :)
> + * after the appropriate time for additional feedback has passed, if the patch has not yet
> + been merged to the relevant tree by the committer, it should be treated as though it had,
> + in that any additional changes needed to it must be addressed by a follow-on patch, rather
> + than rework of the original.
> + * trivial patches may be merged sooner than described above at the tree committer's
> + discretion.
Is it a trivial patch or should I wait 2 weeks before merging this one?
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
next prev parent reply other threads:[~2017-02-21 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 12:02 [PATCH] doc: add details on requirements for patch ack and merge Bruce Richardson
2017-02-21 14:12 ` Thomas Monjalon [this message]
2017-02-21 14:15 ` Bruce Richardson
2017-02-21 16:16 ` Mcnamara, John
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=5210332.Rcp5tEyIor@xps13 \
--to=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.