From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Zapolskiy Date: Mon, 26 Mar 2012 20:49:05 +0300 Subject: [U-Boot] Patchwork housekeeping In-Reply-To: <158450D6-3CB2-4B5F-900D-A23BA8DB6848@freescale.com> References: <4F70A7D3.9000200@mleia.com> <158450D6-3CB2-4B5F-900D-A23BA8DB6848@freescale.com> Message-ID: <4F70AC11.5070405@mleia.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 26.03.2012 20:36, Andy Fleming wrote: > > On Mar 26, 2012, at 12:30 PM, Vladimir Zapolskiy wrote: > >> Hi Graeme, >> >> On 22.03.2012 04:58, Graeme Russ wrote: >>> 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/' >>> 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 >> http://patchwork.ozlabs.org/patch/135526/ >> http://patchwork.ozlabs.org/patch/135699/ >> http://patchwork.ozlabs.org/patch/135697/ >> http://patchwork.ozlabs.org/patch/135698/ >> >> That's the list of patches sent in January, still no progress. >> >>> 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 >> I marked the patches as `awaiting upstream'. > > > Awaiting upstream means that the patches have been applied already, and are waiting for Wolfgang's pull. I suspect this is not the case for your patches. If it is the case, then there's probably no need to mention it, as Wolfgang will eventually pull that tree. > Thanks for correction, I haven't found literally a state `Waiting' among options as it was recommended by Graeme, however I have to change it certainly. Should it be `Under Review' or which state, if a patch is valid, but hasn't been applied yet? -- Vladimir