On Mon, Apr 28, 2008 at 02:17:45AM -0700, David Miller wrote:
I'd say the best solution is to do both.
Many people active only in some area want to read only stuff affecting
their area and not linux-kernel that averaged at 525 emails per day in
February.
But when I have time I skim over patches on linux-kernel, and when I see
in the diffstat that a Makefile or Kconfig file gets touched I check
whether I can spot any bugs there (and other people sometimes also spot
bugs in patches for areas they aren't active in).
And starting regression tracking was only possible since most bug
reports went to linux-kernel, not only to a gazillion different lists.
That's why it might make sense to have everything on both specialized
lists and linux-kernel.
If it is wanted to reduce the volume on linux-kernel, offloading the
sending of patches to some new kernel-patches mailing list might be
an option. OTOH, patches and the discussion of patches seems to be
the signal on linux-kernel, not the noise..
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--