From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id AD23C40BDA0 for ; Tue, 21 Sep 2010 15:23:07 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.89 X-Spam-Level: X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msjCWFkCQ94E; Tue, 21 Sep 2010 15:22:57 -0700 (PDT) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 237B640BC9C; Tue, 21 Sep 2010 15:22:57 -0700 (PDT) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id B54E5568E45; Tue, 21 Sep 2010 15:22:56 -0700 (PDT) From: Carl Worth To: Jameson Rollins , notmuch@notmuchmail.org Subject: Re: notmuch development In-Reply-To: <87lj6ukdtj.fsf@servo.finestructure.net> References: <87k4men8gx.fsf@yoom.home.cworth.org> <87lj6ukdtj.fsf@servo.finestructure.net> User-Agent: Notmuch/0.3.1-90-g8071c5c (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Tue, 21 Sep 2010 15:22:56 -0700 Message-ID: <87bp7qn3cv.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2010 22:23:07 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Tue, 21 Sep 2010 17:05:12 -0400, Jameson Rollins 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. =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMmTBA6JDdNq8qSWgRAvElAKCYH88hg/hHvcYQ3lJmNcZFHPYhiwCgj/8I eF2M0L5MTtyDL6u2RiLtN50= =jOts -----END PGP SIGNATURE----- --=-=-=--