From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: a dedicated list for build error reports?
Date: Mon, 22 Oct 2012 08:43:57 +0000 [thread overview]
Message-ID: <20121022084357.GA8237@localhost> (raw)
In-Reply-To: <20121018130146.GA11433@localhost>
On Mon, Oct 22, 2012 at 10:26:18AM +0200, Julia Lawall wrote:
> > However there are other lots of static check warnings that do need
> > manual check, which are now reported via private emails to Yuanhan and
> > me. If any one is interested in analyzing these possibly false
> > warnings and making bug fixing patches out of them, you'll be warmly
> > welcomed! :-)
>
> If you could send me any Coccinelle warnings with both the report and the
> concerned file, I would be happy to take a look at them, as time permits.
That'd be great. I'll add you to the private CC list for coccinelle
warnings. When you are to do anything about the received private error
report, a simple group reply like "I'll handle this" or "It's a false
warning", plus the fact that we are in different time zone, should be
enough to avoid conflicts between the few people CCed. :)
Thanks,
Fengguang
> > However it also means you'll not see many of the responses from the
> > developers. Since the majority trees are not tied to a mailing list,
> > many reports will become private emails if not CC kernel-janitors.
>
> Personally, I am more interested in just being aware of what is going on,
> but it is a good point that without a mailing list, there is no record of
> the whole exchange, which is probably unfortunate.
>
> julia
next prev parent reply other threads:[~2012-10-22 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 13:01 a dedicated list for build error reports? Fengguang Wu
2012-10-18 19:07 ` David Miller
2012-10-18 23:22 ` Fengguang Wu
2012-10-22 6:52 ` Dan Carpenter
2012-10-22 7:30 ` Julia Lawall
2012-10-22 8:18 ` Fengguang Wu
2012-10-22 8:26 ` Julia Lawall
2012-10-22 8:43 ` Fengguang Wu [this message]
2012-10-22 8:55 ` Julia Lawall
2012-10-22 9:23 ` Dan Carpenter
2012-10-22 9:34 ` Fengguang Wu
2012-10-22 10:14 ` 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=20121022084357.GA8237@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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