public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Custodian changes, using Patchwork
Date: Thu, 18 Nov 2010 06:43:18 -0500	[thread overview]
Message-ID: <201011180643.20457.vapier@gentoo.org> (raw)
In-Reply-To: <4CE50C84.2050609@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 

  reply	other threads:[~2010-11-18 11:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 10:22 [U-Boot] [STATUS] Custodian changes, using Patchwork Wolfgang Denk
2010-11-12 10:55 ` Kumar Gala
2010-11-12 11:11 ` Michal Simek
2010-11-12 12:38   ` Wolfgang Denk
2010-11-17  7:57   ` Stephan Linz
2010-11-17 12:58     ` Wolfgang Denk
2010-11-17 13:10       ` Stephan Linz
2010-11-18  9:41       ` Mike Frysinger
2010-11-18 11:22         ` Stefano Babic
2010-11-18 11:43           ` Mike Frysinger [this message]
2010-11-18 12:58             ` Wolfgang Denk
2010-11-18 12:46         ` Wolfgang Denk
2010-11-18 18:46           ` Mike Frysinger
2010-11-18 19:11             ` Wolfgang Denk
2010-11-12 11:59 ` Albert ARIBAUD
2010-11-12 12:17 ` Stefan Roese
2010-11-12 12:19 ` Reinhard Meyer
2010-11-12 12:45 ` Heiko Schocher
2010-11-12 13:18 ` Anatolij Gustschin
2010-11-12 13:26 ` Michal Simek
2010-11-12 13:32 ` Scott McNutt
2010-11-12 14:01   ` Stefano Babic
2010-11-12 13:59 ` Detlev Zundel
2010-11-12 14:03 ` Marek Vasut
2010-11-12 17:54 ` Scott Wood
2010-11-12 20:03 ` Remy Bohmer
2010-11-12 20:11 ` Jerry Van baren
2010-11-12 20:54   ` Graeme Russ
2010-11-13  0:00 ` Paulraj, Sandeep
2010-11-13 12:14   ` Prafulla Wadaskar
2010-11-15  1:39     ` Minkyu Kang
2010-11-13  2:35 ` Mike Frysinger
2010-11-15  2:25 ` Jin Zhengxiong-R64188
2010-11-15  8:31 ` Daniel Hellstrom
2010-11-16 20:46 ` Andy Fleming
2010-11-17  1:10   ` Marek Vasut
2010-11-17  1:16 ` Nobuhiro Iwamatsu
  -- strict thread matches above, loose matches on Subject: below --
2010-11-15  3:45 macpaul at andestech.com
2010-11-16  2:16 macpaul at andestech.com

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=201011180643.20457.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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