From: Jaroslav Kysela <perex@suse.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA update 0.9.6
Date: Mon, 28 Jul 2003 15:17:24 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307281451220.28950-100000@pnote.perex-int.cz> (raw)
In-Reply-To: <20030728134359.A2558@infradead.org>
On Mon, 28 Jul 2003, Christoph Hellwig wrote:
> On Mon, Jul 28, 2003 at 02:24:24PM +0200, Jaroslav Kysela wrote:
> > <perex@suse.cz> (03/07/28 1.1597)
> > ALSA 0.9.6 update
> > - added __setup() to all midlevel modules
> > - sequencer protocol 1.0.1
> > - added timestamping flags for ports
> > - OSS PCM emulation
> > - fixed write() behaviour
> > - added two new options no-silence & whole-frag
> > - a try to fix OOPSes caused in the rate plugin
> > - emu10k1 driver
> > - more support for Audigy/Audigy2 EX
> > - fixed soundfont locking
> > - sb16 driver
> > - fixed fm_res handling (and proc OOPS)
>
> Any chance you could finally submit individual changes as patches /
> changesets like everyone else does? For the new primary sound driver
> ALSA has quite a bit too much CVS mentality, these monthly or whatever
> updates make it really hard to track individual changes and you have
> a rather bad track record of backing out changes done in mainline
> in the meantime..
Although I understand your complains, you have still a chance to compare
both sources - our ALSA CVS tree and linux BK tree to find the full
code history.
But the changesets are really great, so I am thinking to switch the ALSA
repository from CVS to BK soon. It will help to propagate changes better.
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
next prev parent reply other threads:[~2003-07-28 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:24 [PATCH] ALSA update 0.9.6 Jaroslav Kysela
2003-07-28 12:43 ` Christoph Hellwig
2003-07-28 13:17 ` Jaroslav Kysela [this message]
2003-07-28 13:23 ` Christoph Hellwig
2003-07-29 18:00 ` juan l.
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=Pine.LNX.4.44.0307281451220.28950-100000@pnote.perex-int.cz \
--to=perex@suse.cz \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).