All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: a dedicated list for build error reports?
Date: Thu, 18 Oct 2012 13:01:46 +0000	[thread overview]
Message-ID: <20121018130146.GA11433@localhost> (raw)

On Thu, Oct 18, 2012 at 03:45:22PM +0300, Dan Carpenter wrote:
> On Wed, Oct 17, 2012 at 11:10:42AM +0200, Luis G.F wrote:
> > unsubscribe kernel-janitors
> 
> Uh.  Obviously this isn't the right way to unsubscribe.  You have to
> send the email to majordomo@vger.kernel.org and not to the list.
> 
> But I do think we should maybe find another list for Fengguang's
> emails?  It's sort of a lot higher traffic than before and sort of a
> different flavour.

Agreed.. I'm afraid that my report titles are much more messy than
the normal emails and there could be a dozen of such reports per day.

It may be more clean to send the build error/warning reports to a
standalone list.

> I still will want to subscribe to the emails, but it would be better
> to use a different list.  Apparently Dave Miller didn't like the
> idea of creating a special list for it because he didn't like the
> emails in the first place.  But now I think everyone likes them a
> lot.  It might be worth asking again.

CC Dave Miller for possible new inputs.

Thanks,
Fengguang

             reply	other threads:[~2012-10-18 13:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 13:01 Fengguang Wu [this message]
2012-10-18 19:07 ` a dedicated list for build error reports? 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
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=20121018130146.GA11433@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.