From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: dmix bugs. sounds very broken up.
Date: Tue, 02 Sep 2003 14:20:43 +0100 [thread overview]
Message-ID: <3F54992B.1060800@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0309021232410.29300@pnote.perex-int.cz>
Jaroslav Kysela wrote:
>
> (2)
>
> Problem with uninitialized pcm->info value is fixed in CVS.
>
>
It seems to be impossible to get anything from the sf.net anonymous cvs.
Just try to follow the "CVS Web interface" link from the alsa web page.
I never appears. That is the same interface the anonymouse cvs user
would use.
I use kernel 2.6test4.
Would it be possible to create a nightly patch file, that would compare
the alsa cvs, with the kernel 2.6test4, and create a patch file for us
to download. It would be ideal if the patch was a progressive patch, in
that with each change to the cvs, it just adds a new section of the
patch file, instead of creating a unified patch of all the cvs checkins.
In this way, if I used the first patch, and then the cvs gets updated, I
could download the latest patch, do a diff between it and the previous
one I applied, and be left with just the new patches I needed.
Cheers
James
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-02 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 0:59 dmix bugs. sounds very broken up James Courtier-Dutton
2003-09-01 6:08 ` Jaroslav Kysela
2003-09-01 23:08 ` James Courtier-Dutton
[not found] ` <Pine.LNX.4.53.0309021232410.29300@pnote.perex-int.cz>
2003-09-02 11:50 ` James Courtier-Dutton
2003-09-04 9:46 ` Jaroslav Kysela
2003-09-09 8:05 ` Safe to call snd_pcm_close after failed snd_pcm_open? Arve Knudsen
2003-09-09 9:04 ` Jaroslav Kysela
2003-09-02 13:20 ` James Courtier-Dutton [this message]
2003-09-02 15:19 ` dmix bugs. sounds very broken up Jaroslav Kysela
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=3F54992B.1060800@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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.