From: David Henningsson <david.henningsson@canonical.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: alsa-asoc-devel?
Date: Fri, 06 Aug 2010 13:06:58 +0200 [thread overview]
Message-ID: <4C5BECD2.4050208@canonical.com> (raw)
In-Reply-To: <1281091726.3077.6.camel@odin>
2010-08-06 12:48, Liam Girdwood skrev:
> On Fri, 2010-08-06 at 10:38 +0200, David Henningsson wrote:
>> Hi,
>>
>> There is a lot of asoc traffic on this list, and I assume many people
>> following this list are not interested in ASoC patches.
>>
>> Have you considered splitting the alsa-devel mailing list into an
>> alsa-asoc-devel mailing list, for ASoC specific stuff, and alsa-devel
>> for everything else?
>
> IMO, I think it's pretty much fine where it is atm. It's easy enough to
> filter the posts between ASoC, HDA, OSS etc if you are interested in a
> particular area. Moving the list would also mean core ALSA changes may
> not be fully discussed by ASoC developers/users etc.
I'm not saying ASoC developers and users should stop subscribing to
alsa-devel, if they want to know about core ALSA changes.
Also, filtering is easy enough for local mailboxes, but not for people
following the list via gmane.org, or when looking through alsa-devel's
archives.
Let's hear if more people has something to say about this proposal. If
I'm the only one thinking that a split would be good, obviously it
should stay the way it is :-)
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-08-06 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 8:38 alsa-asoc-devel? David Henningsson
2010-08-06 10:48 ` alsa-asoc-devel? Liam Girdwood
2010-08-06 11:06 ` David Henningsson [this message]
2010-08-06 15:53 ` alsa-asoc-devel? Timur Tabi
2010-08-06 11:31 ` alsa-asoc-devel? Mark Brown
2010-08-06 11:37 ` alsa-asoc-devel? Mark Brown
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=4C5BECD2.4050208@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.