linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org
Cc: Troy Rollo <troy@corvu.com.au>
Subject: RFC/slightly offtopic: Automatic patchwork status updates
Date: Wed, 27 Sep 2006 15:28:48 +1000	[thread overview]
Message-ID: <200609271528.49260.jk@ozlabs.org> (raw)

Hi all,

For some time now, we've been running patchwork on the linuxppc and 
cbe-oss-dev lists. For those who haven't seen it, it collects and 
tracks patches posted to the lists, and shows them here:

  http://patchwork.ozlabs.org/linuxppc
and
  http://patchwork.ozlabs.org/cbe-oss-dev

However, the patch 'state' (eg, accepted, rejected, debug only, changes 
requested) doesn't get updated very often, as it can be an unnecessary 
burden on the maintainers.

All this information is available from the actual upstream tree itself, 
so essentially patchwork *should* be able to just mirror the state.

So, I'd like to get a bit of discussion on how we can get this (or at 
least most of it!) done automatically. For instance, can we come up 
with a scheme that can detect if a patch has made it into paulus' tree 
with some reasonable error rate?

If we can get something sketched up, I'll implement & integrate into 
patchwork. Seeing as this is an own-time project for me though, there 
will probably be a little latency in the process ;)

Cheers,


Jeremy

PS. do we need to create a separate patchwork list and move discussion 
there?

             reply	other threads:[~2006-09-27  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  5:28 Jeremy Kerr [this message]
2006-09-27  6:26 ` RFC/slightly offtopic: Automatic patchwork status updates Michael Neuling

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=200609271528.49260.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=troy@corvu.com.au \
    /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).