[alsa-devel] [BUG] New Kernel Bugs
brong at fastmail.fm
Thu Nov 15 05:16:13 CET 2007
On Wed, Nov 14, 2007 at 12:46:24PM +0100, Rene Herman wrote:
> On 14-11-07 11:07, David Miller wrote:
> Added Jaroslav and Takashi to the already extensive CC....
>> From: Russell King <rmk+lkml at arm.linux.org.uk>
>>> So, when are you creating a replacement alsa-devel mailing list on
>>> vger? That's also subscribers-only.
>> The operative term is "alternative" rather than "replacement".
>> Perhaps this misunderstanding is what you're so upset about.
>> And yes, that alsa list bugs the crap out of me too. I'm more than
>> happy to provide an alternative for that one as well.
> alsa-devel at alsa-project.org is not subscriber-only. Same as that arm list,
> it's _moderated_ for non-subscribers and given that I and other moderators
> have been doing our best to moderate quickly (I tend to stay logged in to
> the moderation interface all day for example) what specifically bugged the
> crap out of you? It's not something a poster needs to concern himself with.
Totally unrelated - I sent something to the kolab mailing list a couple
of days ago (it's moderated for non subscribers) informing them that I
had found the cause of some Cyrus bugs that they had problems with in
the past and providing a link to my post to the cyrus list with the
It sat in the moderation queue and then was rejected with "non
subscriber post to subscription only list". Not only was the reponse a
day later when I had moved on to other things, but it got me really
pissed off that I had put some effort into providing a good quality post
that outlined the specific issues and how they applied to their project,
and had been summarily dismissed, probably without the effort being put
There's no way for a non-subscriber to know in advance if the list they
are trying to post to will do that to them, completely negating the
effort put in to writing something worthwhile to inform that community.
It's insular, and it sucks.
So yeah, my attitude now is that the Kolab folks can go screw themselves
and track down the fix on their own or wait until I've convinced
upstream to accept the fixes (likely) and they have moved to the new
version (unlikely for a long time, and meanwhile they're missing out on
the performance increases that having a more stable skiplist library
would give them)
I'm sure if I had something that I considered worth informing the ALSA
project of, I'd be wary of spending the same effort writing a good
post knowing it may be dropped in between the by a list moderator just
selecing all and bouncing them.
More information about the Alsa-devel