All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Custodian changes, using Patchwork
Date: Thu, 18 Nov 2010 20:11:32 +0100	[thread overview]
Message-ID: <20101118191132.9D8E914E647@gemini.denx.de> (raw)
In-Reply-To: <201011181346.23452.vapier@gentoo.org>

Dear Mike Frysinger,

In message <201011181346.23452.vapier@gentoo.org> you wrote:
>
> > You (as a custodian) can "delegate" patches to a specific maintainer.
> > I. e. you would not mark them as "net", but delegate them to the
> > network custodian.
> 
> right, but atm that is you, so there isnt much of a way to differentiate 
> between the massive common patches that go to you and just network ones

That's true.  BUt it's still better if the patch is explicitly on my
todo list than it's being left unassigned.  As soon as a new net
custodian volunteers I can still re-delgate everything he is willing
to swallow.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
There are two ways to write error-free programs. Only the  third  one
works.

  reply	other threads:[~2010-11-18 19:11 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
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 [this message]
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
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=20101118191132.9D8E914E647@gemini.denx.de \
    --to=wd@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.