From: Krzysztof Halasa <khc@pm.waw.pl>
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 20:16:53 +0100 [thread overview]
Message-ID: <m3odrdiyje.fsf@defiant.localdomain> (raw)
In-Reply-To: <20061110085311.54fd65f2.rdunlap@xenotime.net> (Randy Dunlap's message of "Fri, 10 Nov 2006 08:53:11 -0800")
Randy Dunlap <rdunlap@xenotime.net> writes:
>> * LKML is an overloaded communication channel, do we need:
>> linux-bugs@vger.kernel.org ?
Not sure if LKML is overloaded - subject filtering etc. And people
expect they will be Ccopied if they are, for example, maintainers.
It's not the list for everybody, though.
> 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 don't like this idea as implemented now - it's probably fine for
subsystem maintainers but it's prohibitive for an occasional submitter.
But... specific lists would make sense if - and only if:
- they are always mirrored to something like LKML so one doesn't need
to subscribe to every possible list (as they appear).
- they are open as LKML is (no specific subscription required to post)
This way one could discuss things with/on a specific list (subscribed
by subsystem maintainers and other interested people) and everyone
reading the general list (or more general?) would see it too.
We could have a hierarchy:
- specific lists like lmkl-usb-ohci
- more general lkml-usb
- lkml, seeing all mail
This way every mail sent to lkml-usb-ohci would be sent to lkml-usb,
and lkml-usb would be copied to lkml as well (I imagine some duplicate
elimination would be a plus).
Anyone could discuss ohci writing to lkml-usb-ohci, discuss general
USB writing to lkml-usb etc. Anyone subscribed to any of the above
lists would see the traffic they are interested in, without a need
for constant subscribing.
I assume the lists would be hosted on one domain to make it easy
to post and perhaps to enable it to work at all.
If some form of sender address verification/scoring was in use I think
it would be smart to recognize all people subscribed to more general
lists to be "known" for this purpose (i.e., people subscribed to
lkml would be considered "subscribed" while posting to lkml-usb-ohci).
Having written all of the above I now like the idea so be prepared to
fight me hard if you don't :-)
Perhaps I could even help implementing it in some unspecified so
called "free time".
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-11-11 19:16 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 4:57 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
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 ` Krzysztof Halasa [this message]
2006-11-11 19:15 ` A proposal; making 2.6.20 a bugfix only version 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=m3odrdiyje.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--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
Powered by JetHome