From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Drake Wilson <drake@libcom.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: documentation - yeah right!
Date: Wed, 21 May 2003 14:02:43 +0900 [thread overview]
Message-ID: <3ECB0873.7060108@boosthardware.com> (raw)
In-Reply-To: 20030520195353.A24020@octothorpe.dyndns.org
Drake Wilson wrote:
>
> This is a lacuna, albeit one which may be remediable by
> non-ALSA-developers. I am researching the sequencer interface for a
> program I am writing; afterwards, I plan to attempt some better
> tutorial-level documentation for it, assuming I am able to with
> respect to logistics and knowledge organization.
>
Yes please. We have been waiting for someone to take this up for a
while. It appears that the people who do work with the sequencer
interface are either too busy or too shy to write something which
everyone can reference.
It would be the last arrow in the quiver IMO.
You will get a lot of support for anything you submit BTW.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-21 5:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 20:10 documentation - yeah right! Cliff Bradshaw
2003-05-20 20:16 ` Jaroslav Kysela
2003-05-20 20:31 ` Josh Green
2003-05-20 20:52 ` Kai Vehmanen
2003-05-20 22:11 ` David Stuart
2003-05-20 22:08 ` Paul Davis
2003-05-20 23:53 ` Drake Wilson
2003-05-21 5:02 ` Patrick Shirkey [this message]
2003-05-21 7:34 ` Giuliano Pochini
2003-05-21 14:43 ` Richard Cochran
2003-05-21 15:24 ` Paul Davis
2003-05-21 15:50 ` Paul Davis
[not found] ` <200305211518.h4LFI2jE027163@mail.cs.umass.edu>
2003-05-21 15:59 ` Richard Cochran
2003-05-21 16:52 ` Kai Vehmanen
2003-05-21 17:16 ` Richard Cochran
2003-05-21 17:36 ` Kai Vehmanen
2003-05-21 17:39 ` Jaroslav Kysela
2003-05-21 17:49 ` Paul Davis
2003-05-21 17:03 ` Paul Davis
[not found] ` <200305211657.h4LGvKjE024721@mail.cs.umass.edu>
2003-05-21 18:08 ` Richard Cochran
2003-05-22 1:28 ` Patrick Shirkey
2003-05-21 16:09 ` Richard Cochran
2003-05-21 16:44 ` Paul Davis
2003-05-22 13:16 ` PCI write barrier Giuliano Pochini
2003-05-23 10:30 ` Takashi Iwai
2003-05-22 12:47 ` documentation - yeah right! Takashi Iwai
2003-05-22 13:39 ` Jaroslav Kysela
2003-05-22 14:51 ` Pieter Palmers
2003-05-22 14:18 ` Richard Cochran
2003-05-22 15:33 ` Takashi Iwai
2003-05-22 16:57 ` Jack O'Quin
2003-05-22 17:03 ` Patrick Shirkey
2003-05-22 17:08 ` Richard Cochran
2003-07-11 0:23 ` i810 - no sound from cvs snapshot Richard Cochran
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=3ECB0873.7060108@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=drake@libcom.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.