linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Cc: linux-mtd@lists.infradead.org, bazaar-ng@lists.canonical.com,
	cbe-oss-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: New Patchwork beta
Date: Thu, 21 Aug 2008 18:22:26 +0800	[thread overview]
Message-ID: <200808211822.27786.jk@ozlabs.org> (raw)

Hi all,

I've just put up a new beta of patchwork:

  http://patchwork2.ozlabs.org/

I intend to replace the existing patchwork with the new code, but would 
like to get it tested first. There aren't many patches in the system at 
the moment, but it'll receive patches from the relevant lists. I'll 
also import a set of existing mails tomorrow, to give some sample data 
to test with.

One important note - after beta testing, I'm planning to clear the test 
database and start from scratch. So, don't go spending too much time 
updating patches!

However, have a play with the new site, let me know what breaks, and any 
suggestions for changing, and we can work towards a full replacement 
for the current site.

Some differences from the old patchwork:

  * Patches can now be 'delegated' to other maintainers - this means
    that maintainers can offload subsystem-specific patches to other
    maintainers.

  * Anyone can create an account, and work with bundles, and manage
    their own patches.

  * Pagination. No more 10MB patch lists!

  * Bundles can be made public, allow users to share patchsets

  * Better filtering interface

Project Maintainers:

  Create an account, then send me your username, and I'll add maintainer
  privileges to your account. Again, don't go too crazy with the   
  maintaining work, as it'll all be cleared out once we replace 
  patchwork.ozlabs.org

  Also: bazaar-ng, linux-mtd and linux-embedded folks: are you still
  using patchwork?

Existing patches:

  After talking to the powerpc maintainers, we've decided that we're
  going to start with a clean slate, and not import patches from the
  existing patchwork database. If you'd prefer to keep current patches
  for your project, let me know. This will be a bit of work, but I'm
  sure we can work something out.

Happy patchworking,


Jeremy

             reply	other threads:[~2008-08-21 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 10:22 Jeremy Kerr [this message]
2008-08-21 20:32 ` New Patchwork beta Kumar Gala
2008-08-21 22:52   ` Josh Boyer
2008-08-22  8:12     ` Kumar Gala
2008-08-22  8:55       ` [Cbe-oss-dev] " Jeremy Kerr
2008-08-22 10:05         ` Kumar Gala

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=200808211822.27786.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=bazaar-ng@lists.canonical.com \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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).