On Fri, Mar 20, 2009 at 11:04 PM, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> wrote: > Devin, > > Please, don't invert the things. > > I am the one that is trying to defend the need of keeping the backport, while > most of you are trying to convince to me to just drop it, since developers will > run the bleeding edge -rc. > > With the argument that developers shouldn't run the bleeding edge kernel, I'd > say you should do it. This is the way kernel development is. You shouldn't send > something upstream, if your patch doesn't run with the latest -rc. In my case, > I have my alpha environment for such tests, separated from the environment I > write my code. This allows me to do development on a more stable environment, > being sure that it will keep running with the latest kernel. > > With the respect of using the backported environment for developing, you can do > it, if you want. It will be available for all usages. Have you ever seen the > approach I'm proposing at my backported tree? I can't see why you couldn't use > it for development also. Mauro, When this thread was started, it was about dropping support for kernels < 2.6.22. However, it has turned into a thread about moving to git and dropping support for *all* kernels less than the bleeding edge -rc candidate (only supporting them through a backport system for testers). The two are very different things. I agree with the general consensus that we should raise the "minimum bar" from 2.6.16 to 2.6.22. And I also believe that we need to ensure that we do not want to lose testers by requiring them to run the latest kernel release. However, now we are talking about what the *developers* are expected to run. What has now been proposed is changing the build system such that developers must run the latest -rc kernel, which I do not believe is a good idea. It makes it easier for the maintainer to merge patches, however at the cost of the other developers trying to focus on v4l-dvb development without having to worry about whether this week's -rc kernel is going to work in their environment. It already takes me half an hour to checkout and build the latest v4l-dvb tree. Telling me that now I'm going to have to download and build the entire kernel on a weekly basis, as well as deal with whatever crap gets broken in my environment, is too much for many developers who don't work for a distribution vendor. For a developer working nights and weekends on this stuff, this ends up being a significant fraction of my development time. I just want it to be clear that there are developers who are not willing to run the latest -rc kernel just for the luxury of being able to contribute to v4l-dvb. Devin -- Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- 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
