Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell-2FmhHzymoG5BDgjK7y7TUQ@public.gmane.org>
To: The Linux Audio Developers' Mailing List
	<linux-audio-dev-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org>
Cc: alsa-devel
	<alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org
Subject: Re: Firewire Breakout-Boxes
Date: Fri, 27 Aug 2004 12:44:34 -0400	[thread overview]
Message-ID: <1093625074.837.18.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.HPX.4.33n.0408271409310.16637-100000-uTWBjZk67LHpX0crx97Rjzs8JdKFpwrh@public.gmane.org>

On Fri, 2004-08-27 at 08:15, Clemens Ladisch wrote:
> Daniel Wagner wrote:
> > > You really should get in contact with the ALSA guys.
> >
> > I have already posted a message there couple of weeks ago.
> 
> Messages from non-subscribers are routed to /dev/null because there
> isn't a moderator.
> 

Is this really necessary in this day and age?  The spam problem is
solved, it has been for a while now.  man spamassassin.

Lee

       reply	other threads:[~2004-08-27 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.HPX.4.33n.0408271409310.16637-100000@studcom.urz.uni-halle.de>
     [not found] ` <Pine.HPX.4.33n.0408271409310.16637-100000-uTWBjZk67LHpX0crx97Rjzs8JdKFpwrh@public.gmane.org>
2004-08-27 16:44   ` Lee Revell [this message]
     [not found]     ` <1093625074.837.18.camel-sMXKvD5kdRZ9Itub2Jo68g@public.gmane.org>
2004-08-27 17:51       ` Firewire Breakout-Boxes Dan Hollis
     [not found]         ` <Pine.LNX.4.44.0408271050420.3162-100000-XlhkJ1vUGd+swHjBqO1tUg@public.gmane.org>
2004-08-27 18:18           ` Lee Revell
     [not found]             ` <1093630709.837.42.camel-sMXKvD5kdRZ9Itub2Jo68g@public.gmane.org>
2004-08-27 19:08               ` [Alsa-devel] " Dan Hollis

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=1093625074.837.18.camel@krustophenia.net \
    --to=rlrevell-2fmhhzymog5bdgjk7y7tuq@public.gmane.org \
    --cc=alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org \
    --cc=linux-audio-dev-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.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