On Tue, 21 Sep 2010 17:05:12 -0400, Jameson Rollins <jrollins@finestructure.net> wrote:
> Hey, Carl.  The most obvious thing I can think of is delegating some
> lieutenants to handle processing patches.  There definitely are some
> worthy candidates (who are kind of already doing this already).  Even if
> they're not actually pushing patches into a canonical repo, they could
> at least vet in-coming patches and prep things for your review.  If they
> could present you with branches that are potentially "ready to go" it
> might make things a lot easier for you, especially when you're in a
> crunch.

Yes. Other people can definitely help me, particular as I gain trust in
their ability to review, accept, and reject patches in a similar way to
what I would have done myself.

I do like that patches are in general sent to the mailing list, and I'd
like that to continue. I use searches based on the list messages to
determine patches that I still need to review, (though, obviously I'm
quite a ways behind in this process).

As people review and accept patches, I'd love to receive mail addressed
specifically to me, (can copy the list as well, of course), with
pointers to git repositories that have "accepted" patches integrated
into them.

That will definitely help me prioritize pulling such patches into the
canonical repository.

-Carl

-- 
carl.d.worth@intel.com