Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: iriXx <m@iriXx.org>
To: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: future ALSA development
Date: Tue, 24 Jun 2003 09:28:45 +0100	[thread overview]
Message-ID: <3EF80BBD.6060803@iriXx.org> (raw)
In-Reply-To: 3EF77D90.5080209@folkwang-hochschule.de



Joern Nettingsmeier wrote:

> true if you only consider alsa. but on most systems, libxml2 is there 
> anyway. <underwear type="asbestos">and imvho xml is less a matter of 
> taste than lisp.</underwear> and xml is way easier to handle in other 
> contexts (i'm thinking of auto.configuration stuff etc.)
> otoh, the embedded guys will probably not like it, but then memory is 
> becoming cheaper by the minute, and its additional size will be a moot 
> point in the very near future.
> 
> 

ROFL im just reading my email over breakfast and had a splurting coffee 
moment wondering how many of us could see your underwear..... ;-)

m~

> 


-- 
        |\      _,,,---,,_
  ZZZzz /,`.-'`'    -.  ;-;;,_     HTTP 503: Too Busy
       |,4-  ) )-,_. ,\ (  `'-'
     '---''(_/--'  `-'\_) fL


  .::. www.iriXx.org .::. www.copyleftmedia.org.uk .::.

             gnupg key ID: AEB7A31E





-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

  parent reply	other threads:[~2003-06-24  8:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 19:10 future ALSA development Jaroslav Kysela
2003-06-23 11:14 ` Takashi Iwai
2003-06-23 12:01   ` Jaroslav Kysela
2003-06-23 13:13     ` Takashi Iwai
2003-06-23 13:41       ` Paul Davis
2003-06-23 13:51         ` Takashi Iwai
2003-06-23 14:18           ` Paul Davis
2003-06-23 22:22     ` Joern Nettingsmeier
2003-06-24  7:51       ` mru
2003-06-24  8:14       ` Jaroslav Kysela
2003-06-24 11:19         ` Abramo Bagnara
2003-06-24 11:43         ` Paul Davis
2003-06-24 11:56           ` Jaroslav Kysela
2003-06-24 12:16             ` Paul Davis
2003-06-24 17:11               ` Takashi Iwai
2003-06-24 18:28                 ` Jaroslav Kysela
2003-06-25 17:49                   ` PCMCIA In Kernel Or In ALSA Driver? Len Moskowitz
2003-06-25 18:51                     ` Jaroslav Kysela
2003-06-30 10:17                   ` future ALSA development Takashi Iwai
2003-06-24  8:28       ` iriXx [this message]
2003-07-03 13:39       ` Kai Vehmanen
2003-07-07 11:26         ` Takashi Iwai
2003-10-01  9:37           ` ALSA in embedded use (was: Re: future ALSA development) Kai Vehmanen
2003-10-01 13:13             ` Takashi Iwai
2003-06-24 12:52   ` future ALSA development Giuliano Pochini
2003-06-24 13:04     ` Jaroslav Kysela
2003-06-24 17:12       ` Takashi Iwai
2003-07-03 14:21 ` Kai Vehmanen
2003-07-03 14:36   ` Kai Vehmanen
2003-07-03 16:05 ` Thomas Charbonnel
2003-07-07 11:37   ` Takashi Iwai

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=3EF80BBD.6060803@iriXx.org \
    --to=m@irixx.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=nettings@folkwang-hochschule.de \
    /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