public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patchwork housekeeping
Date: Thu, 22 Mar 2012 07:45:34 +0100	[thread overview]
Message-ID: <201203220745.34397.marek.vasut@gmail.com> (raw)
In-Reply-To: <CALButC+gO1prxBhpKH=SKS+cVbN-vQqVN4tJUUTn3AfJf1SovA@mail.gmail.com>

Dear Graeme Russ,

> Hello Custodians and Mailing List Aficionados,
> 
> I don't know if anyone has noticed, but patchwork is starting to collect
> a rather large amount of cruft.
> 
> I occasionally jump onto patchwork and do a little housekeeping by marking
> updated patches as 'Superceeded' and anything applied by Wolfgang as
> 'Accepted' (There may be a few patches that have been applied to custodian
> tress that I marked as 'Accepted' when really they should have been marked
> as 'Awaiting Upstream')
> 
> I really don't mind doing this housekeeping, but I would like to make a
> few suggestions that will make the work a little easier:
> 
>  - If you are a custodian:
>     o When you apply a patch to your repo, can you please assign it to
>       yourself in patchwork and set it to 'Awaiting Upstream'
>     o Reply to the ML with 'Applied to <repo>/<branch>'
>     o When you send a pull request, create a bundle with all the patches
>       that are to be pulled (you can create the bundle early and add
>       patches as you apply them)
>     o When Wolfgang pulls your repo, go to the bundle and mark all the
>       patches 'Accepted'
> 
>  - If you are a patch submitter:
>     o Visit http://patchwork.ozlabs.org/project/uboot/list/
>     o Search for your patches by following the 'Filters'link and entering
>       your name
>     o Send and email (with 'patchwork' somewhere in the subject) to the ML
>       with a list of patches that you submitted say more than one month
>       ago. For each patch, please indicate if the patch is:
>         * Superseded - By another patch (either by you or someone else)
>         * Not Applicable - The patch can be ignored (was an RFC, was due
>           to a misunderstanding, another patch did the same thing, etc)
>         * Applied - Has been applied (state the repo and branch)
>         * Rejected - Patch has been officially rejected
>         * Waiting - You believe the patch is still valid but has not been
>           applied (send a ping as a reply to the patch on the mailing list
>           as well
>         * Other - Please describe what state you feel the patch is in
> 
> Once I get the raw list down to a manageable level, I'll start to look at
> the leftovers...

WAT ? Yet another ruleset ... and a long one while at that. Maybe we should 
cobble together an "U-Boot contributors guidebook" ... printed edition with 1k 
pages ;-D

We really need to make it easier for people to contribute to u-boot, these long 
rulesets only ward people away.

> 
> Regards,
> 
> "Your friendly Patchwork janitor" Graeme

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-22  6:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  2:58 [U-Boot] Patchwork housekeeping Graeme Russ
2012-03-22  6:45 ` Marek Vasut [this message]
2012-03-22 11:15   ` Graeme Russ
2012-03-22 11:35     ` Marek Vasut
2012-03-22 15:08 ` Tom Rini
2012-03-22 16:09   ` McClintock Matthew-B29882
2012-03-22 17:22     ` Tom Rini
2012-03-22 19:15       ` Khem Raj
2012-03-22 16:21 ` Scott Wood
2012-03-26 17:30 ` Vladimir Zapolskiy
2012-03-26 17:36   ` Andy Fleming
2012-03-26 17:49     ` Vladimir Zapolskiy

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=201203220745.34397.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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