On Thu, 22 Jun 2006, Takashi Iwai wrote: > > Or worse, finding out that we have to be backwards compatible with an > > API that was never used! > > If it was never used, we can simply abandon the old ioctl :) > (Of course, better not to have such one.) I think that the situation with the out-of-tree development is not ideal. I commited my first TLV patch as soon as possible to show the way. It's really a smart patch without any additonal code to show the simplest way to implement TLV. The callback enhancement is also a quick and smart evolution for the TLV implementation so I'd like to commit it also now, but reactions like "we should wait more time" prevents me to do it. I think that the policy should be: Send a patch proposal to alsa-devel and if none has serious objections in two weeks, put it to the HG repo, otherwise we'll end with huge changes which can be hardly verified in the commit time. I would prefer a step-by-step evolution and bug-fixing in several commits rather than a big patch which does all at once. Jaroslav ----- Jaroslav Kysela <perex@xxxxxxx> Linux Kernel Sound Maintainer ALSA Project, SUSE Labs Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
