Hi, A few developers asked me how I'm working with the git trees for development. So, I decided to write a few quick notes about it at the wiki: http://linuxtv.org/wiki/index.php/Using_a_git_driver_development_tree I also added the script I use to remove the modules from the memory. Based on my own experience, using the Git tree instead of Mercurial speed up my development time when working with IR, especially since I had to touch at the input system core, to add two new ioctls. As input core is not at the Mercurial, if I was using the old way, I would have to deal with both mercurial and upstream trees. The drawback of doing a full compilation of the upstream kernel is not bad for me, since I always test the latest kernel anyway. Of course, other people may have different experiences. That's why we're keep supporting the mercurial trees ;) Btw, in order to help developers to work with git, I'm trying to preserve the git tree with the latest stable Linus kernel version (currently, 2.6.33), plus the v4l-dvb new drivers. So, I intend to backport from upstream only with 2.6.34. PS.: with respect to the pending patches, I was abroad last week, and I'm currently with a very high volume of patches, some requiring lots of tests. My intention is to merge the great majority of the patches until the end of this weekend. -- Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
