From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Triplett Subject: Meet the new maintainer Date: Thu, 2 Jul 2009 14:43:50 -0700 Message-ID: <20090702214349.GA19009@feather> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from slow3-v.mail.gandi.net ([217.70.178.89]:52550 "EHLO slow3-v.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754187AbZGBWQB (ORCPT ); Thu, 2 Jul 2009 18:16:01 -0400 Received: from relay3-v.mail.gandi.net (relay3-v.mail.gandi.net [217.70.178.77]) by slow3-v.mail.gandi.net (Postfix) with ESMTP id 9B36F83CED for ; Thu, 2 Jul 2009 23:50:54 +0200 (CEST) Received: from feather (pool-173-50-250-234.ptldor.fios.verizon.net [173.50.250.234]) by relay3-v.mail.gandi.net (Postfix) with ESMTP id 2907CB9FF for ; Thu, 2 Jul 2009 23:50:19 +0200 (CEST) Content-Disposition: inline Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: linux-sparse@vger.kernel.org I originally started maintaining Sparse as a result of trying to merge = various patches related to my PhD research. =A0Now I don't have frequent Sparse= patches of my own anymore, and due to my PhD studies and other projects, I've b= ecome significantly less responsive, while Sparse itself has enjoyed increase= d development interest. Thus, it seems only fair that I should hand off maintainership to someone else who has a pile of patches they want to m= erge. Christopher Li has done an excellent job hacking on Sparse, and has already demonstrated the ability to maintain a Sparse tree and merge other people's patches. I believe Chris would make an excellent maintainer for Sparse. I still plan to listen in on the Sparse community, and perhaps submit some future patches, but effective immediately^Wa while ago, Chris will start running the show and accepting your patches and contributions. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-sparse"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html