From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Thu, 18 Nov 2010 06:43:18 -0500 Subject: [U-Boot] [STATUS] Custodian changes, using Patchwork In-Reply-To: <4CE50C84.2050609@denx.de> References: <20101112102231.5F71E1522C0@gemini.denx.de> <201011180441.47800.vapier@gentoo.org> <4CE50C84.2050609@denx.de> Message-ID: <201011180643.20457.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thursday, November 18, 2010 06:22:44 Stefano Babic wrote: > On 11/18/2010 10:41 AM, Mike Frysinger wrote: > > patchwork should hopefully help ? ive never used it before so i dont > > know of its capabilities. is there a way to mark things as "net" ? > > I never used, too. I have seen there is the possibility to set a filter > for incoming patches, and at least if "net" is in the subject, we get a > short list. No idea if there are some other ways. too bad many people dont prefix their patch summaries accordingly :( > Anyway, are there some hints for the maintainers how to work with > patchwork ? i looked, but couldnt find any actual documents > Should we already mark ourself as delegate for the patches > we think we have to manage ? i think so ... seems like a pretty organic setup rather than a few people whose job it is to monitor/update. set the delegates for patches that lack them, and update patch statuses for ones you know have been accepted/superseded/whatever. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20101118/75a567cf/attachment.pgp