From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Mihaela Vitalariu <admiralwolverine@gmail.com>
Cc: Alsa-devel@alsa-project.org
Subject: Re: how do you people debug ALSA?
Date: Mon, 21 Jan 2008 13:04:05 +0100 [thread overview]
Message-ID: <20080121120405.GI9896@lug-owl.de> (raw)
In-Reply-To: <ef33e0240801210111l569c27f4k624d9b37dd33fce8@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 749 bytes --]
On Mon, 2008-01-21 11:11:25 +0200, Mihaela Vitalariu <admiralwolverine@gmail.com> wrote:
>
> How do you ALSA developers debug the ALSA code?
Which part of it? ALSA is a quite large project, starting with kernel
code at the lowest level and ending at application level on the other
end.
> If you have any hints please reply.
What specifically doesn't work? The question above is far from being
detailed enough to help you. It's like "My car is broken, how do I fix
it?" without any comment which kind of problem you face (engine,
wheels, ...)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: http://perl.plover.com/Questions.html
the second :
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-01-21 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 9:11 how do you people debug ALSA? Mihaela Vitalariu
2008-01-21 12:04 ` Jan-Benedict Glaw [this message]
2008-01-21 15:13 ` Mihaela Vitalariu
2008-01-21 15:39 ` Timur Tabi
2008-01-22 17:21 ` John Utz
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 20:25 mazarick
2008-01-22 8:45 ` Clemens Ladisch
2008-01-22 12:14 ` Claudio Matsuoka
2008-01-23 11:09 ` 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=20080121120405.GI9896@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=Alsa-devel@alsa-project.org \
--cc=admiralwolverine@gmail.com \
/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.