On Thu, 5 Mar 2009, Guennadi Liakhovetski wrote: > On Wed, 4 Mar 2009, Mauro Carvalho Chehab wrote: > > Beside the fact that we don't need to strip support for legacy kernels, the > > advantage of using this method is that we can evolute to a new development > > model. As several developers already required, we should really use the > > standard -git tree as everybody's else. This will simplify a lot the way we > > work, and give us more agility to send patches upstream. > > > > With this backport script, plus the current v4l-dvb building systems, and after > > having all backport rules properly mapped, we can generate a "test tree" > > based on -git drivers/media, for the users to test the drivers against their > > kernels, and still use a clean tree for development. > > Sorry, switching to git is great, but just to make sure I understood you > right: by "-git drivers/media" you don't mean it is going to be a git tree > of only drivers/media, but it is going to be a normal complete Linux > kernel tree, right? So there will be no way we can test a driver without switching to a new kernel hourly? And there is no way we can test someone else's tree without compiling an entirely new kernel and rebooting? And every tree we want to work on requires a complete copy of the entire kernel source? -- 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
