From: Christopher Li <sparse@chrisli.org>
To: Thomas Graf <tgraf@suug.ch>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Sparse maintainership (was: [PATCH] sparse: Make -Werror turn warnigns into errors)
Date: Wed, 24 Sep 2014 23:05:45 +0800 [thread overview]
Message-ID: <CANeU7QkryNQCNp62SDC8SA=yn05CN-OteYGw99_-BOwGQjJxPQ@mail.gmail.com> (raw)
In-Reply-To: <20140924123140.GF24298@casper.infradead.org>
On Wed, Sep 24, 2014 at 8:31 PM, Thomas Graf <tgraf@suug.ch> wrote:
> Are you still maintaining sparse Christopher?
>
Sorry has been slacking.
Let me take a look of your patch right now.
Chris
next prev parent reply other threads:[~2014-09-24 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 18:54 [PATCH] sparse: Make -Werror turn warnigns into errors Thomas Graf
2014-09-03 18:59 ` josh
2014-09-03 19:08 ` Thomas Graf
2014-09-24 12:31 ` Sparse maintainership (was: [PATCH] sparse: Make -Werror turn warnigns into errors) Thomas Graf
2014-09-24 15:05 ` Christopher Li [this message]
2014-09-24 15:24 ` [PATCH] sparse: Make -Werror turn warnigns into errors Christopher Li
2014-09-24 15:42 ` Thomas Graf
2014-09-24 23:16 ` Christopher Li
2014-09-25 2:27 ` Christopher Li
2014-09-25 2:46 ` Christopher Li
2014-09-25 8:12 ` Thomas Graf
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='CANeU7QkryNQCNp62SDC8SA=yn05CN-OteYGw99_-BOwGQjJxPQ@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).