All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Patchwork
Date: Wed, 11 Nov 2009 15:55:29 +0100	[thread overview]
Message-ID: <20091111145529.GA11567@linux-mips.org> (raw)

Many of you may already have heared about it - I've installed patchwork
on http://patchwork.linux-mips.org.  The system is now running mostly
flawless so time to announce it.

What is patchwork?

Patchwork is a patch tracking system.  It is subscribed to the linux-mips
mailing list and automatically sifts throuogh the list for patches posted.
The web interface allows anybody to see which patches are still pending,
are under review, have been applied or rejected.

Patchwork also keeps track of replies to patches so it's often easier to
follow than by using a mail reader.  Patchworks also collects Acked-by:,
Signed-off-By: lines so when downloading a patch from the web interface
the log messages will have been updated to contain the updated tags.

Why is patchwork a good thing?

It allows a maintainer to keep a good overview over all the pending patches.
Unlike many previous systems that were implemented or suggested it doesn't
get into the way of established patch submission and handling practices
but rather provides a tool to automate a part of necessary procedures.

What does patchworks mean for patch submissions?

Patchwork is subscribed to the linux-mips mailing list.  So it will only
keep track of patches that have been posted to the linux-mips mailing list
but not of patches that have been sent in private to me.  This is a problem
so I'm considering to reject patches that have not been submitted to the
mailing list as a matter of policy.

Beyond that it's largely up to the patch submitter.  For a submitter who
doesn't use patchwork things will work the same way they used to work.

What new advanced features deos patchwork offer to submitters?

Submitters can create an account on patchworks.  They can change the
status of their patches - which are identified as theirs by the submitter's
email address - for example when they wish withdraw a patch because it
was found faulty or are about to send a better revision.

There is also a feature to create patch bundles from several patches which
then can be downloaded as a single download.

Which patches are tracked in patchworks?

I've installed patchworks about four weeks ago.  For testing purposes and
also to ensure I've not dropped anything on the floor I've fed the
mailing list archives back to June 2009 into patchworks, then manually
walked through the hundreds of patches to ensure all patches have been
handled.

If you've sent patches that have not been applied yet and don't show up
in patchworks as new or under review, then please resent your patches.

  Ralf

             reply	other threads:[~2009-11-11 14:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 14:55 Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-15 20:55 Patchwork Ryan Eatmon
2022-03-15 20:55 Patchwork Ryan Eatmon
2019-05-03 17:18 patchwork akuster808
2019-05-12 18:04 ` patchwork akuster808
2019-05-13  7:27   ` patchwork Zoran Stojsavljevic
2019-05-13  7:32   ` patchwork Mark Hatle
2019-04-17 10:17 patchwork John Crispin
2019-04-23 14:44 ` patchwork Kalle Valo
2019-04-23 14:49   ` patchwork Jeremy Kerr
2019-04-23 15:06     ` patchwork Kalle Valo
2019-05-06 12:53       ` patchwork Kalle Valo
2011-12-07 11:35 Patchwork Ralf Baechle
2010-04-09  5:46 Initial work on an Android SDK via openembedded Angus Lees
2010-04-10 13:01 ` GNUtoo
2010-04-15 17:56   ` Patchwork Konrad Mattheis
2010-04-15 18:59     ` Patchwork Philip Balister
2009-11-06 15:37 patchwork Chris Mason

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=20091111145529.GA11567@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.