From: Julia Lawall <julia.lawall@lip6.fr>
To: Fengguang Wu <wfg@linux.intel.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Pekka Enberg <penberg@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christopher Li <sparse@chrisli.org>,
Josh Triplett <josh@freedesktop.org>,
Linus Torvalds <torvalds@ppc970.osdl.org>
Subject: Re: automated warning notifications
Date: Fri, 15 Jun 2012 06:40:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1206150639130.1864@hadrien> (raw)
In-Reply-To: <20120615075810.GA13206@localhost>
> > Eventually I think we will want to set up a mailing list for this or
> > we will start sending duplicate messages.
>
> Fair enough. How can we setup the mailing list? Once the list up, it
> would be trivial for me to send sparse warnings out there.
I'm not completely sure that a mailing list would completely eliminate
duplicate messages. But still, it could be the place for people who are
interested in seeing such messages to go to, so it seems like a good
thing. I would be happy to contribute content :)
julia
next prev parent reply other threads:[~2012-06-15 10:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 17:25 automated warning notifications Dan Carpenter
2012-06-15 1:48 ` Fengguang Wu
2012-06-15 7:12 ` Dan Carpenter
2012-06-15 7:58 ` Fengguang Wu
2012-06-15 8:31 ` Josh Triplett
2012-06-15 8:54 ` Fengguang Wu
2012-06-15 16:48 ` Randy Dunlap
2012-06-16 9:17 ` Fengguang Wu
2012-06-16 17:44 ` Randy Dunlap
2012-06-15 10:40 ` Julia Lawall [this message]
2012-06-15 11:19 ` Dan Carpenter
2012-06-15 13:33 ` Peter Senna Tschudin
2012-06-15 13:53 ` Dan Carpenter
2012-06-15 15:49 ` Peter Senna Tschudin
2012-06-15 14:34 ` Fengguang Wu
2012-06-16 7:50 ` Cong Wang
2012-06-16 9:01 ` Fengguang Wu
2012-07-02 12:45 ` Dan Carpenter
2012-07-06 3:07 ` Fengguang Wu
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=alpine.DEB.2.02.1206150639130.1864@hadrien \
--to=julia.lawall@lip6.fr \
--cc=dan.carpenter@oracle.com \
--cc=josh@freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@ppc970.osdl.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wfg@linux.intel.com \
/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