From: "Qiu, Michael" <michael.qiu@intel.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>,
Neil Horman <nhorman@tuxdriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Mon, 4 May 2015 12:39:37 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E602860466B50C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20150501171854.GC595@fuloong-minipc.musicnaut.iki.fi>
On 5/2/2015 1:19 AM, Aaro Koskinen wrote:
> Hi,
>
> On Fri, May 01, 2015 at 12:45:12PM -0400, Neil Horman wrote:
>>> - GitHub manages the patches via pull requests and can be easily seen
>>> via a web browser.
>>> - The down side is you do have to use a web browser to do some work, but
>>> the bulk of the everyday work would be done as it is today.
>>> - I think we all have a web browser now :-)
>> 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.
> I agree. Having a web browser interface for reviews etc. is acceptable
> only if people can still continue to use e-mail if they prefer.
> I don't know how github works in this regard but patches should still
> appear on the mailing list and it should be still possible to comment
> them via mailing list.
How it comes?
As I know if use github, the maillist will be meaningless.
And do you know some area on the earth maybe have issue with github?
Anyway, Github is OK to me, but I prefer maillist :).
Thanks,
Michael
> A.
>
next prev parent reply other threads:[~2015-05-04 12:39 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 [this message]
2015-05-01 17:31 ` Matthew Hall
2015-05-01 17:45 ` Wiles, Keith
2015-05-01 18:48 ` Neil Horman
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=533710CFB86FA344BFBF2D6802E602860466B50C@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=aaro.koskinen@iki.fi \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
/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).