Hello, First of all I want to thank you very much for giving us this great mobile platform. MeeGo is just amazing!
I know that the MeeGo kernel process has been a big debate before (I have read the archives). I cloned the kernel-source tree and saw that it only contains patches against different kernel versions. Just was wondering what are the benefits/disadvantages using this approach (set of patches) over having a complete different kernel tree? Option 1: Set of patches tree This makes a lot of sense since most of the development should be made upstream. The meego kernel should only be a small delta from kernel.org tree. But if the meego kernel is supposed to be a small delta from kernel.org. I wonder if maybe would it be better to just work against linux-next and don't even have a meego kernel. The kernel team could create the packages for distribution and order builds in OBS but with sources from kernel.org or another "official" tree. Patches could go through linux-next, subsystems trees (i.e: net-2.6.git,pcmcia-2.6.git,etc) and drivers that are not ready to go upstream could go through staging. As a matter of fact, staging also begun as a "set of patches" tree and later was merged in linux-next as a subdirectory. Option 2: Complete MeeGo tree In the other hand If there is a lot of development in the meego kernel (i.e: lots of drivers and new architectures), maybe there could be a meego-2.6.git tree where most of the development would happen. This tree could be keep in sync with linux-next so patches would not conflict and one could send patches to either tree. It would serve as a staging area for the code that is going to be push upstream. I'm not by any means criticizing the current kernel development process. I just want to give my two cents because I saw such an open environment both in code as in ideas Thanks a lot Best regards, ----------------------------------------- Javier MartÃnez Canillas +595 981 88 66 58 _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
