From: Jeff Garzik <jeff@garzik.org>
To: Josh Triplett <josh@kernel.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Meet the new maintainer
Date: Thu, 02 Jul 2009 18:27:52 -0400 [thread overview]
Message-ID: <4A4D3468.1010202@garzik.org> (raw)
In-Reply-To: <20090702214349.GA19009@feather>
Josh Triplett wrote:
> I originally started maintaining Sparse as a result of trying to merge various
> patches related to my PhD research. Now I don't have frequent Sparse patches
> of my own anymore, and due to my PhD studies and other projects, I've become
> significantly less responsive, while Sparse itself has enjoyed increased
> 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 merge.
>
> 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.
Agreed!
> 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.
Can you weigh in on the licensing threads, pretty please? That is still
blocked on you, AFAIK.
Jeff
next prev parent reply other threads:[~2009-07-02 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 21:43 Meet the new maintainer Josh Triplett
2009-07-02 22:27 ` Jeff Garzik [this message]
2009-07-02 23:08 ` Sparse licensing Josh Triplett
2010-01-21 12:08 ` Dan Carpenter
2009-07-03 0:34 ` Meet the new maintainer Chris Li
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=4A4D3468.1010202@garzik.org \
--to=jeff@garzik.org \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).