netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: jeff@garzik.org, linville@tuxdriver.com
Subject: patchwork for netdev
Date: Thu, 18 Sep 2008 16:56:07 -0700 (PDT)	[thread overview]
Message-ID: <20080918.165607.55765591.davem@davemloft.net> (raw)


During the kernel summit, Paul Mackerras gave an excellent presention
on the patchwork web based tool they are using for powerpc platform
development.

In a nutshell, it's a web tool that gets fed by a mailing list and
records patches.  Administrators for a "project" can change the
state of the patches, edit them, put them into bundles, etc.
And everyone can look at the state of the patch queue and also
look up older patches that were rejected, deferred, accepted, etc.

It looks like it can streamline our workflow as well as give people
a place to see what state their patch is in.  So I've asked the
ozlabs folks to create a "netdev" project.

See for yourself:

	http://patchwork.ozlabs.org/project/netdev/list/

Currently I am the admin for this project.

It might be nice if Jeff Garzik created an account for himself,
so I can get him marked as an admin as well, since driver patches
get funneled there too.

John Linville, on the other hand, may wish to ask the ozlabs folks
to add a linux-wireless project and admin that project.

John, I'll send you a contact under private cover that you can use
if interested.

             reply	other threads:[~2008-09-18 23:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 23:56 David Miller [this message]
2008-09-19  0:01 ` patchwork for netdev Randy.Dunlap
2008-09-19  0:05   ` David Miller
2008-09-19  0:09     ` Randy.Dunlap
2008-09-19  0:12       ` David Miller
2008-09-19  0:13         ` Randy.Dunlap
2008-09-19  7:13       ` Christoph Hellwig
2008-09-19  0:28     ` Rick Jones
2008-09-19  2:11       ` David Miller
2008-09-23  1:08         ` Simon Horman
2008-09-23  2:44           ` David Miller
2008-09-23  8:24             ` Benjamin Herrenschmidt
2008-09-23 10:44               ` Jeremy Kerr

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=20080918.165607.55765591.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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).