DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] patchwork for dpdk.org?
Date: Wed, 19 Mar 2014 11:28:19 +0100	[thread overview]
Message-ID: <3378875.vgnsJ2253J@xps13> (raw)
In-Reply-To: <CADEmHi3NDBT+50GAKaAXVKSKebpCeSTnBGBc6o_rTR-BchhkQQ@mail.gmail.com>

18/03/2014 16:31, Kyle Mestery:
> stephen@networkplumber.org wrote:
> > Anybody considered setting up patchwork to track patches on this list?
> > 
> > If not familiar, patchwork is a back end which maintainers and developers
> > can keep track of patches submitted and make sure of the status (accepted,
> > rejected, review, etc).
> 
> +1 for patchwork.

I agree. Installing patchwork on dpdk.org is planned.

I wasn't available last weeks so I'm starting to review the recent patches.
By the way, it's good news that we now need such tools to manage 
contributions.
-- 
Thomas

  reply	other threads:[~2014-03-19 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 20:58 Stephen Hemminger
2014-03-18 21:31 ` Kyle Mestery
2014-03-19 10:28   ` Thomas Monjalon [this message]
2014-03-24 16:05     ` Thomas Monjalon

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=3378875.vgnsJ2253J@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    /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).