From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaro Koskinen Subject: Re: GitHub sandbox for the DPDK community Date: Fri, 1 May 2015 22:59:32 +0300 Message-ID: <20150501195932.GD595@fuloong-minipc.musicnaut.iki.fi> References: <20150501110914.182dcfb1@urahara> <20150501194951.GA25199@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Matthew Hall Return-path: Content-Disposition: inline In-Reply-To: <20150501194951.GA25199-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Fri, May 01, 2015 at 12:49:51PM -0700, Matthew Hall wrote: > On Fri, May 01, 2015 at 11:09:14AM -0700, Stephen Hemminger wrote: > > With email, the patches are right in front of developers and easier to quote > > for review comments. > > Right in front of that subset of developers who do everything kernel-style, > perhaps yes. But this sort of workflow is in the minority these days, pretty > much every other project I've worked on besides the kernel used graphical > merging tools for this to make things easier to follow for the uninitiated. Projects like GCC, GLIBC, binutils, busybox, etc or what? A.