On Mon, 21 Mar 2005, Lee Revell wrote:
> > > This one is fixed in ALSA CVS.
> >
> > But not in http://linux-sound.bkbits.net/linux-sound yet. How does stuff
> > propagate from ALSA CVS into bk?
>
> The ALSA maintainers periodically ask Linus to pull from the linux-sound
> tree. But that's just the general "ALSA update" process.
>
> I'm not aware of a mechanism for getting critical fixes like this in
> ASAP. The last few have been shepherded through manually by various
> people. Looks like we need a better system.
I am trying to sync the linux-sound BK tree every week with our CVS.
For "urgent" fixes we need to find another faster way. Hopefully, they
are in most cases small enough, so they might be propagated automagically.
I already proposed special "tag" in our CVS commit policy, so we can
identify these patches / changesets.
I will try to prepare some useable tool in few weeks.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
