From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: a dedicated list for build error reports?
Date: Mon, 22 Oct 2012 09:23:52 +0000 [thread overview]
Message-ID: <20121022092352.GB7329@mwanda> (raw)
In-Reply-To: <20121018130146.GA11433@localhost>
On Mon, Oct 22, 2012 at 04:18:20PM +0800, Fengguang Wu wrote:
>
> Good idea. I can do the summary if the too many reports are a problem
> for the list.
I would do fine with the summary as well. Perhaps if I could add a
procmail filter so it would go into its own mailbox. I would modify
my scripts to grep for the error before sending a dublicate report.
The thing about the reports are that it's not actually anything that
janitors can help out with. Normally it's in some tree that no one
has and the author takes care of the fix.
regards,
dan carpenter
next prev parent reply other threads:[~2012-10-22 9:23 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
2012-10-22 8:55 ` Julia Lawall
2012-10-22 9:23 ` Dan Carpenter [this message]
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=20121022092352.GB7329@mwanda \
--to=dan.carpenter@oracle.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