From: Julia Lawall <julia.lawall@lip6.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: a dedicated list for build error reports?
Date: Mon, 22 Oct 2012 08:26:18 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1210221022070.2026@hadrien> (raw)
In-Reply-To: <20121018130146.GA11433@localhost>
> 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.
> 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:26 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 [this message]
2012-10-22 8:43 ` Fengguang Wu
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=alpine.DEB.2.02.1210221022070.2026@hadrien \
--to=julia.lawall@lip6.fr \
--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