Dear Graeme Russ, > Hi Marek, > > On 03/22/2012 05:45 PM, Marek Vasut wrote: > > 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 > > The submission rules (http://www.denx.de/wiki/U-Boot/Patches) are pretty > clear and concise (I've added a not about starting the subject with a tag)
Some distilled down version for first-time comers won't hurt of that page. > > > We really need to make it easier for people to contribute to u-boot, > > these long rulesets only ward people away. > > This patchwork cleanup should really only be a once off to try and get > things cleaned up a bit. There are patches in patchwork from 2009, if we > can get some of the stale patches cleaned out (and contact the submitters > to see if they are interested in resubmitting or verifying re-based > patches) then we will all be better off. Agreed > > Nothing is more discouraging to patch submitters than patches that get > ignored. Yes > > Regards, > > Graeme Thanks for working on this, Graeme, I really appreciate that Best regards, Marek Vasut _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
