DPDK patches and discussions
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Thu, 7 May 2015 11:26:18 -0400	[thread overview]
Message-ID: <20150507152617.GE14981@tuxdriver.com> (raw)
In-Reply-To: <5549CCEC.8090606@redhat.com>

On Wed, May 06, 2015 at 11:12:28AM +0300, Panu Matilainen wrote:

> Forcing a change of tools and workflows on everybody WILL create ill-will if
> nothing else.
> 
> Also please realize that not everybody sees GitHub as the greatest thing
> since sliced bread. It has quite some "Hotel California" aspects to it, and
> actually the imago of an average GH project is not that great: there are so
> many badly run and abandoned projects there that the first thought when I
> hear the word GitHub is "oh no, not one of those again" rather than "cool".
> I know I'm not alone in that thinking.

GitHub -- the SourceForge of the 21st century!

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2015-05-07 15:30 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
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 [this message]
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=20150507152617.GE14981@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=pmatilai@redhat.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).