From: Chris Li <christ.li@gmail.com>
To: Josh Triplett <josh@kernel.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Meet the new maintainer
Date: Thu, 2 Jul 2009 17:34:00 -0700 [thread overview]
Message-ID: <70318cbf0907021734t165d6881td00057ca8fc0ac26@mail.gmail.com> (raw)
In-Reply-To: <20090702214349.GA19009@feather>
On Thu, Jul 2, 2009 at 2:43 PM, Josh Triplett<josh@kernel.org> 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.
>
> 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.
I want to thank Josh for his wonderful contribution for the sparse project.
I still have a lot of to learn to maintain a project like sparse. I
will try my best.
Let me share you with my view of the project. In my mind, sparse has
two roles:
1) A general purpose C compiler front end.
2) A sanitize checker for the Linux kernel source.
I like to see the project continue to evolve in this two directions. At the same
time I want to maintain the current style of lean and fast.
Now I like to heard your view of the project as well. Where you want to
the project go. After all, this is a community project.
Thanks for all your support.
Chris
--
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
prev parent reply other threads:[~2009-07-03 0:33 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
2009-07-02 23:08 ` Sparse licensing Josh Triplett
2010-01-21 12:08 ` Dan Carpenter
2009-07-03 0:34 ` Chris Li [this message]
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=70318cbf0907021734t165d6881td00057ca8fc0ac26@mail.gmail.com \
--to=christ.li@gmail.com \
--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).