public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: proposal: feed smaller mailing lists into linux-kernel, addlinux-kernel-core and linux-kernel-bugs
Date: Thu, 20 Dec 2001 13:09:48 +0100	[thread overview]
Message-ID: <3C21D50C.5020605@debian.org> (raw)
In-Reply-To: <fa.dptrd8v.o4g2i8@ifi.uio.no> <fa.i1142kv.1r0cr0q@ifi.uio.no>

David S. Miller wrote:
 > Absolutely no way.  Forwarding "all the little other lists" into
 > linux-kernel is not going to make things better.

But creating a linux-bug list with this policy:

- The stable kernel series point to this lists
- Annoncement to new kernel point to the normal list
    (the bug to newer kernel are classified 'development')
- Kernel maintainers post to the bug list the 'annonces'
    the of solved bugs
- All discussion about kernel series 0.01, 2.0 and 2.2
    (bug hunting series) should go in this new list

In this manner we:
- have a bug tracking system (a' la Linux)
- We can grep quikly to see if a new bug to an
    old kernel is aready closed.

The new list, IMHO, doesn't duplicate trafic,
but I think it don't reduce much of linux-kernel traffic.
(But provide a quicker references of the know bugs).

     giacomo


       reply	other threads:[~2001-12-20 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.dptrd8v.o4g2i8@ifi.uio.no>
     [not found] ` <fa.i1142kv.1r0cr0q@ifi.uio.no>
2001-12-20 12:09   ` Giacomo Catenazzi [this message]
2001-12-20 12:21     ` proposal: feed smaller mailing lists into linux-kernel, addlinux-kernel-core and linux-kernel-bugs Momchil Velikov

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=3C21D50C.5020605@debian.org \
    --to=cate@debian.org \
    --cc=linux-kernel@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