From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Cc: alsa-user
Subject: snd_pcm_link documentation
Date: Sat, 11 Sep 2004 21:59:57 -0400 [thread overview]
Message-ID: <1094954396.1306.102.camel@krustophenia.net> (raw)
Hmm, I think I may have an explanation for the perennial favorite
complain about ALSA, "there's no documentation!". It's a Google bug.
Googling for "snd_pcm_link documentation" produces only 15 results:
http://www.google.com/search?q=snd_pcm_link+documentation&num=50&hl=en&lr=&ie=UTF-8&safe=off&output=search
The correct page does not appear at all:
http://www.alsa-project.org/alsa-doc/alsa-lib/group___p_c_m.html#a61
How is it that the full API docs have been posted on alsa-project.org
for ages, and the best Google can do is one lousy page of code examples
and old mailing list postings?
No wonder so many people (myself included) get so worked up about the
"lack of ALSA documentation"; there effectively isn't any unless you
already know exactly where to look.
Probably all the internal links in the Doxygen-derived HTML are
triggering some heuristic to detect Google-spamming (or whatever the
heck they call it).
Lee
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
reply other threads:[~2004-09-12 1:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1094954396.1306.102.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/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.