From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wiles, Keith" Subject: Re: GitHub sandbox for the DPDK community Date: Fri, 1 May 2015 17:45:27 +0000 Message-ID: References: <20150501164512.GB27756@hmsreliant.think-freely.org> <20150501173108.GA24714@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Matthew Hall , Neil Horman Return-path: In-Reply-To: <20150501173108.GA24714-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org> Content-Language: en-US Content-ID: <42D5124F0CE0724996259A6FC298B730-ral2JQCrhuEAvxtiuMwx3w@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 5/1/15, 12:31 PM, "Matthew Hall" wrote: >Normally I'm a big command-line supporter. However I have found reviewing >patches by email for me is about the most painful workflow. > >The emails are pages and pages. > >The replies from commenters are buried in the walls of text. > >Replies to replies keep shifting farther off the edge of the screen. The >code=20 >gets weirder and weirder to try to read. > >Quickly reading over the patchset by scrolling through to get the flavor >of=20 >it, to see if I'm qualified to review it, and look at the parts I >actually=20 >know about is much harder. > >I can go to one place to see every candidate patchset out there, the GH >Pull=20 >Request page. Then I can just sync up the branch and test it on my own >systems=20 >to see if it works, not just try to read it. > >Github automatically minimizes old comments that are already fixed, so >they=20 >don't keep consuming space and mental bandwidth from the review. > >All in all, I'd be able to review more DPDK patches faster with the GH >interface than having them in the mailing list. +1 and very well stated. > >Matthew. >