From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <nhorman@tuxdriver.com>
Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58])
 by dpdk.org (Postfix) with ESMTP id AC1355A3D
 for <dev@dpdk.org>; Fri, 16 Jan 2015 21:01:06 +0100 (CET)
Received: from hmsreliant.think-freely.org
 ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost)
 by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63)
 (envelope-from <nhorman@tuxdriver.com>)
 id 1YCD4k-0003Qf-Ha; Fri, 16 Jan 2015 15:01:03 -0500
Date: Fri, 16 Jan 2015 15:00:57 -0500
From: Neil Horman <nhorman@tuxdriver.com>
To: Matthew Hall <mhall@mhcomputing.net>
Message-ID: <20150116200057.GG27496@hmsreliant.think-freely.org>
References: <20150114122352.63ef79eb@urahara> <2507392.XzU56ErIKp@xps13>
 <20150116172017.GE27496@hmsreliant.think-freely.org>
 <2188823.ZBC1oOX6oS@xps13> <20150116185852.GA29426@mhcomputing.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150116185852.GA29426@mhcomputing.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Score: -2.9 (--)
X-Spam-Status: No
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 20:01:08 -0000

On Fri, Jan 16, 2015 at 10:58:52AM -0800, Matthew Hall wrote:
> On Fri, Jan 16, 2015 at 07:18:19PM +0100, Thomas Monjalon wrote:
> > I'd like to try solving the review challenge first and see what else can be 
> > done after that. Step by step.
> 
> FWIW, I know the kernel guys seem to really love it, but not everybody else 
> has much fun trying to do the reviews reading huge patch emails. I lose a lot 
> of context trying to stare at them in mutt 80x25 console etc.
Well, ok, then don't use mutt, no one mandates it.  You can setup
outlook/thunderbird/evolution/MTA of choice to format email properly for lkml
pretty easily.

> It would be nice 
> if we could have a visual interface with syntax highlighting and comment 
> capabilities, that's easier to read through quickly and clearly, like 
> ReviewBoard, GitHub Pull Request UI, etc. If it had email integration to reply 
> to the patch threads that'd be great too.
> 
Like Gerrit:
https://code.google.com/p/gerrit/

Its easy enough to setup your own instance and point it at your own tree for
review purposes.

> Also if we had some branches available where conceptually related changes are 
> grouped, somebody could check out the branch with some feature they wanted to 
> try, get all the related patches, integrate with their app of choice, and see 
> if the app works successfully with the new feature.
> 
That would be the master branch of a subtree, if the granularity was correct.

> Some of these things like DPDK, it isn't obvious how the feature will help or 
> hurt, until you write some code against it and/or benchmark it first, because 
> some of these features are kind of complicated.
> 
> Another thing... if we had some kind of wiki page, where some of the backend 
> coders could mark themselves as maintainers of all the different features they 
> work on, and more client-side network stack guys like me could express 
> interest in certain features, we could connect the two sides so any given guy 
> knows who can review his bugfix he found, or try out his new patchset to see 
> if it works well in an app.
> 
Thats what the MAINTAINERS file and --subject-prefix options in git-send-email
are commonly used for

Neil