From: James Courtier-Dutton <james.dutton@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [ALSA - driver 0001671]: THIS DRIVER FRICKEN SUCKS
Date: Mon, 2 Jan 2006 12:10:55 +0000 [thread overview]
Message-ID: <ad2655cb0601020410v22a206eev@mail.gmail.com> (raw)
In-Reply-To: <1ad9064044bcdbbf739fc579ecf66c6d@bugtrack.alsa-project.org>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
On 02/01/06, bugtrack@alsa-project.org <bugtrack@alsa-project.org> wrote:
>
>
> Summary: THIS DRIVER FRICKEN SUCKS
> Description:
> WHAT THE HELL WERE YOU GUYS THINKING? YOU WEREN'T!!!! This has got to be
> one of the shitest drivers i've ever used. o i know lets make a driver
> that crashes 99% of the time. it sucks, why the hell should you put it in
> if it sucks? please make this driver better, its a common card, and you
> are so close to a sucessfull driver, i know you can do it!
> ======================================================================
>
> ----------------------------------------------------------------------
> perex - 01-02-06 08:50
> ----------------------------------------------------------------------
> A rude bug report without any additional information. Closed.
>
>
Yes, my ISPs spam trap deleted this before I even saw it!
[-- Attachment #2: Type: text/html, Size: 1335 bytes --]
next prev parent reply other threads:[~2006-01-02 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 7:50 [ALSA - driver 0001671]: THIS DRIVER FRICKEN SUCKS bugtrack
2006-01-02 12:10 ` James Courtier-Dutton [this message]
2006-01-02 19:38 ` Lee Revell
2006-01-02 19:59 ` Peter Zubaj
2006-01-03 12:14 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 2:04 bugtrack
2005-12-25 8:45 ` Eric Shattow
2005-12-22 1:50 bugtrack
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=ad2655cb0601020410v22a206eev@mail.gmail.com \
--to=james.dutton@gmail.com \
--cc=alsa-devel@alsa-project.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