Hi Jaroslav,
I suppose keeping the ALSA CVS as our root would indeed be the best option. Synchronisation of the kernel and our CVS tree could be sort of a challenge since people wil start to submit patches against the kernel tree (and possibly only posted to lkml). On the other hand the diff between CVS and kernel tree should not grow too big, since in that case Linus would start to dislike our patches (as happened with the isdn guys). Frequent synchronisation wil be important, which as a downside involves a lot of bookkeeping which patches have been applied by Linus, and which not (yet). Just some thoughts, Frank. ps: the ALSA merge in the kernel was indeed a great milestone, and I must admit I used it as a good excuse for giving a small party :-) On Thu, Feb 14, 2002 at 05:34:37PM +0100, Jaroslav Kysela wrote: > On Thu, 14 Feb 2002, Takashi Iwai wrote: > > > now a realistic question: > > > > how do we manage the alsa driver codes together with linux 2.5 tree? > > will be like before, i.e. occasionally Jaroslav sends patches to Linus > > (or directly to bk) based on the alsa cvs? > > Yes, I would like to leave the ALSA's CVS repository as root of our > sources. I think that syncing should be done for each new Linux releases. > I take care about it, next days proves my plans. > > Jaroslav > > ----- > Jaroslav Kysela <[EMAIL PROTECTED]> > Linux Kernel Sound Maintainer > ALSA Project http://www.alsa-project.org > SuSE Linux http://www.suse.com > > > > _______________________________________________ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel -- +---- --- -- - - - - | Frank van de Pol -o) A-L-S-A | [EMAIL PROTECTED] /\\ Sounds good! | http://www.alsa-project.org _\_v | Linux - Why use Windows if we have doors available? _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
