public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Hemminger <shemminger@osdl.org>,
	Jesper Juhl <jesper.juhl@gmail.com>, Al Boldi <a1426z@gawab.com>,
	linux-kernel@vger.kernel.org
Subject: Re: A proposal; making 2.6.20 a bugfix only version.
Date: Sat, 11 Nov 2006 08:15:33 +0100	[thread overview]
Message-ID: <20061111071533.GA577@1wt.eu> (raw)
In-Reply-To: <20061110085311.54fd65f2.rdunlap@xenotime.net>

On Fri, Nov 10, 2006 at 08:53:11AM -0800, Randy Dunlap wrote:
> Either that or lkml is/remains for bug reporting and we move development
> somewhere else.  Or my [repeated] preference:
> 
> do development on specific mailing lists (although there would
> likely need to be a fallback list when it's not clear which mailing
> list should be used)

I've been thinking about this too for a while now. There is something
like half of the email volume which are (semi-)automated emails
containing patches moving from a GIT tree to another. I think that
moving this to some linux-dev or something like this would :

  1) reduce the noise on LKML so that problem reports are better caught
  2) reduce the global email volume because instead of sending all these
     emails to 10-20000 persons(?), only maybe a thousand will be subscribed.
  3) reduce even more the latency between post and publication due to 2.

I don't know if others would be interested, in which case it would be wise
to poll on the subject and include Matti and Davem to the discussion.

Regards,
Willy


  parent reply	other threads:[~2006-11-11  7:15 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  4:57 A proposal; making 2.6.20 a bugfix only version Al Boldi
2006-11-09 17:05 ` Stephen Hemminger
2006-11-10 15:52   ` Al Boldi
2006-11-10 16:16     ` Jesper Juhl
2006-11-10 16:42       ` Stephen Hemminger
2006-11-10 16:53         ` Randy Dunlap
2006-11-10 19:33           ` Al Boldi
2006-11-10 19:49             ` Arjan van de Ven
2006-11-10 21:22               ` Al Boldi
2006-11-10 21:31                 ` Stephen Hemminger
2006-11-11  4:15                   ` Al Boldi
2006-11-11  5:09                     ` Stephen Hemminger
2006-11-11  7:23                       ` David Miller
2006-11-11 11:15                         ` Al Boldi
2006-11-11  6:31                     ` Valdis.Kletnieks
2006-11-11 11:15                       ` Al Boldi
2006-11-11  7:15           ` Willy Tarreau [this message]
2006-11-11 12:03             ` Neil Brown
2006-11-11 21:08               ` bugzilla (was Re: A proposal; making 2.6.20 a bugfix only version.) Pavel Machek
2006-11-11 19:16           ` A proposal; making 2.6.20 a bugfix only version Krzysztof Halasa
2006-11-11 19:15         ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-11-08 22:09 Jesper Juhl
2006-11-08 22:22 ` Arjan van de Ven
2006-11-08 22:40   ` Jesper Juhl
2006-11-08 23:05     ` Andreas Mohr
2006-11-08 23:54       ` Jan Engelhardt
2006-11-10 15:15     ` Pavel Machek
2006-11-10 15:48     ` Horst H. von Brand
2006-11-15 21:04       ` Jesper Juhl
2006-11-08 22:51   ` Andrew Morton
2006-11-09  9:26     ` Arjan van de Ven
2006-11-09  9:36       ` Andrew Morton
2006-11-09  9:52         ` Arjan van de Ven
2006-11-09 19:12           ` Andrew Morton
2006-11-09 19:21             ` Arjan van de Ven
2006-11-09 21:11               ` Adrian Bunk
2006-11-09 21:31                 ` Arjan van de Ven
2006-11-09 23:56                   ` Thomas Gleixner
2006-11-10  0:18                     ` Andrew Morton
2006-11-10 17:45                     ` Stefan Richter
2006-11-11 11:00                     ` Martin J. Bligh
2006-11-08 23:28   ` Diego Calleja
2006-11-09  6:48     ` Arjan van de Ven
2006-11-09 12:45       ` Rolf Eike Beer

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=20061111071533.GA577@1wt.eu \
    --to=w@1wt.eu \
    --cc=a1426z@gawab.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=shemminger@osdl.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