From: Matthew Hall <mhall@mhcomputing.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-dev] Proposal for a new Committer model
Date: Thu, 17 Nov 2016 22:00:27 -0800 [thread overview]
Message-ID: <20161118060027.GA17595@mhcomputing.net> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202661F22@IRSMSX103.ger.corp.intel.com>
On Thu, Nov 17, 2016 at 09:20:50AM +0000, Mcnamara, John wrote:
> One committer to master represents a single point of failure and at times can be inefficient.
I have a lot more issues because of slow or inconclusive review of patches
than I do because of committers. Often times they just get rejected in
Patchwork with no feedback. Or it takes forever to get reviews.
I don't think the committer is the right place to point to the single point of
failure.
Matthew.
next prev parent reply other threads:[~2016-11-18 6:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 9:20 Mcnamara, John
2016-11-18 6:00 ` Matthew Hall [this message]
2016-11-18 18:09 ` Neil Horman
2016-11-18 19:06 ` Jerin Jacob
2016-11-20 4:17 ` Stephen Hemminger
2016-11-21 8:52 ` Thomas Monjalon
2016-11-22 19:52 ` Neil Horman
2016-11-22 20:56 ` Ferruh Yigit
2016-11-23 13:48 ` Neil Horman
2016-11-23 14:01 ` Ferruh Yigit
2016-11-23 15:33 ` Neil Horman
2016-11-23 16:21 ` Ferruh Yigit
2016-11-23 20:13 ` Neil Horman
2016-11-24 9:17 ` Thomas Monjalon
2016-11-25 19:55 ` Neil Horman
2016-11-23 8:21 ` Mcnamara, John
2016-11-23 14:11 ` Neil Horman
2016-11-23 15:41 ` Yuanhan Liu
2016-11-23 20:19 ` Neil Horman
2016-11-24 5:53 ` Yuanhan Liu
2016-11-25 20:05 ` Neil Horman
2016-11-29 19:12 ` Neil Horman
2016-11-30 9:58 ` Mcnamara, John
2016-12-02 16:41 ` 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=20161118060027.GA17595@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=moving@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).