From: Paul Davis <paul@linuxaudiosystems.com>
To: Martin Dausel <dauselm@emt.iis.fhg.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: problems with 0.9.8 drivers and rme9652
Date: Wed, 12 Nov 2003 13:03:35 -0500 [thread overview]
Message-ID: <200311121803.hACI3aQC023763@oud.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Wed, 12 Nov 2003 18:30:11 +0100." <3FB26E23.3050903@emt.iis.fhg.de>
1) just a quick note to point out that whether you know it or not, the
email program you are using is sending out copies of your mail in both
plain text and HTML formats. increasingly on the net, there are
filters being put in place that silently dump HTML-formatted
email. some mailing lists will not ever accept such posts. as long as
you do this, you are (1) wasting network bandwidth by sending messages
that are typically more than twice as long as they could be (2) making
it harder for people using traditional email readers to read them (3)
risking the chance that people will never see your mail because its
filtered before reaching their email inbox.
2) as requested, please send the output of lspci -v
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
next prev parent reply other threads:[~2003-11-12 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 16:24 problems with 0.9.8 drivers and rme9652 Martin Dausel
2003-11-12 17:01 ` Paul Davis
2003-11-12 17:30 ` Martin Dausel
2003-11-12 18:03 ` Paul Davis [this message]
2003-11-13 10:10 ` Martin Dausel
[not found] ` <1068750901.22388.1.camel@barbounia>
2003-11-17 12:45 ` Martin Dausel
2003-11-17 12:57 ` Justin Cormack
-- strict thread matches above, loose matches on Subject: below --
2003-11-18 16:05 nick mainsbridge
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=200311121803.hACI3aQC023763@oud.linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dauselm@emt.iis.fhg.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