From: Geoff Beasley <songshop@bizmedia.com.au>
To: alsa-devel@lists.sourceforge.net
Subject: C-Port midi bug.
Date: Mon, 25 Apr 2005 11:31:00 +1000 [thread overview]
Message-ID: <1114392660.4832.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20050424154406.43A4E12C15@sc8-sf-spam2.sourceforge.net>
Is there any news on this issue yet please ? It would be mighty to get
this solved... let me know if I can help test.
Geoff.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next parent reply other threads:[~2005-04-25 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050424154406.43A4E12C15@sc8-sf-spam2.sourceforge.net>
2005-04-25 1:31 ` Geoff Beasley [this message]
2005-04-25 7:44 ` C-Port midi bug Clemens Ladisch
[not found] <1114416346.4749.4.camel@localhost.localdomain>
2005-04-26 7:47 ` Clemens Ladisch
2005-04-27 14:53 ` Clemens Ladisch
2005-04-27 21:06 ` SPAM Filter Konto
2005-04-27 21:14 ` SPAM Filter Konto
[not found] <20050427193028.B7CA288863@sc8-sf-spam1.sourceforge.net>
2005-04-29 7:43 ` gerard van dongen
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=1114392660.4832.1.camel@localhost.localdomain \
--to=songshop@bizmedia.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox