DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Fri, 1 May 2015 14:48:13 -0400	[thread overview]
Message-ID: <20150501184813.GC27756@hmsreliant.think-freely.org> (raw)
In-Reply-To: <20150501173108.GA24714@mhcomputing.net>

On Fri, May 01, 2015 at 10:31:08AM -0700, Matthew Hall wrote:
> On Fri, May 01, 2015 at 12:45:12PM -0400, Neil Horman wrote:
> > Yes, but as you said above, using a web browser doesn't make reviewing patches
> > faster.  In fact, I would assert that it slows the process down, as it prevents
> > quick, easy command line access to patch review (as you have with a properly
> > configured MUA).  That seems like we're going in the opposite direction of at
> > least one problem we would like to solve.
> 
> 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.
> 
So collapse the quoted text (see below)

> The replies from commenters are buried in the walls of text.
> 
Again, collapse the text, many MUA's let you do that, its not a feature unique
to github.

> Replies to replies keep shifting farther off the edge of the screen. The code 
> gets weirder and weirder to try to read.
> 
Text Collapse will reformat that for you.

> Quickly reading over the patchset by scrolling through to get the flavor of 
> it, to see if I'm qualified to review it, and look at the parts I actually 
> know about is much harder.
> 
Thats what the origional post is for, no?  Look at that to determine if you are
qualified to read it.

> I can go to one place to see every candidate patchset out there, the GH Pull 
> Request page. Then I can just sync up the branch and test it on my own systems 
> to see if it works, not just try to read it.
> 
how is that different from a mailing list?  both let you search for posts, and
both allow you to sync git branches (github via git remote/pull, mailing list
via git am)

> Github automatically minimizes old comments that are already fixed, so they 
> don't keep consuming space and mental bandwidth from the review.
An MUA can do that too.  IIRC evolution and thunderbird both have collapse
features.  I'm sure others do too.

> 
> All in all, I'd be able to review more DPDK patches faster with the GH 
> interface than having them in the mailing list.
> 
> Matthew.
> 

  parent reply	other threads:[~2015-05-01 18:48 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 15:56 Wiles, Keith
2015-05-01 16:45 ` Neil Horman
2015-05-01 17:18   ` Aaro Koskinen
2015-05-04 12:39     ` Qiu, Michael
2015-05-01 17:31   ` Matthew Hall
2015-05-01 17:45     ` Wiles, Keith
2015-05-01 18:48     ` Neil Horman [this message]
2015-05-01 19:10       ` Wiles, Keith
2015-05-02  2:59         ` Wiles, Keith
2015-05-03 21:00         ` Neil Horman
2015-05-04  3:51           ` Wiles, Keith
2015-05-04 12:43     ` Qiu, Michael
2015-05-04 17:48       ` Matthew Hall
2015-05-04 18:52         ` Neil Horman
2015-05-05  3:12         ` Wiles, Keith
2015-05-05  3:25           ` Jim Thompson
2015-05-05 13:55             ` Neil Horman
2015-05-05 16:43               ` Wiles, Keith
2015-05-05 17:57                 ` John W. Linville
2015-05-05 18:30                   ` Wiles, Keith
2015-05-05 18:46                     ` John W. Linville
2015-05-05 19:07                 ` Neil Horman
2015-05-05 20:15                   ` Wiles, Keith
2015-05-06  8:12                 ` Panu Matilainen
2015-05-06  8:30                   ` Simon Kågström
2015-05-06  9:00                     ` Panu Matilainen
2015-05-06 10:37                     ` Neil Horman
2015-05-07 15:26                   ` John W. Linville
2015-05-01 18:01   ` Wiles, Keith
2015-05-01 18:09 ` Stephen Hemminger
2015-05-01 18:17   ` Wiles, Keith
2015-05-04 20:34     ` Marc Sune
2015-05-05  2:54       ` Wiles, Keith
2015-05-01 19:49   ` Matthew Hall
2015-05-01 19:59     ` Aaro Koskinen
2015-05-01 20:36       ` Matthew Hall
2015-05-02 11:40         ` Neil Horman
2015-05-02 12:37           ` Thomas F Herbert
2015-05-02 14:07             ` Wiles, Keith
2015-05-02 13:59           ` Wiles, Keith
2015-05-04 21:08             ` Marc Sune
2015-05-05  3:09               ` Wiles, Keith
2015-05-04  6:52 ` Simon
2015-05-04  9:05   ` Marc Sune
2015-05-06 10:11 ` Mcnamara, John
2015-05-06 21:09 ` Thomas Monjalon
2015-05-06 21:37   ` Marc Sune
2015-05-06 23:49     ` Wiles, Keith
2015-05-07  3:37       ` Wiles, Keith
2015-05-12 14:38         ` Thomas Monjalon
2015-05-04  5:08 Wiles, Keith

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=20150501184813.GC27756@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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).