On Tue, May 19, 2009 at 9:35 PM, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> wrote: > Steven, > > Your concerns about testing make sense, but this were already tried in the > past, when Uri started sending their patches at the ML. So, instead of > repeating the same novel, let's merge the patches at the development tree and > ask people to test. > > Yet, I'm keeping the Siano patches at the 'pending' -git tree, where I hold > very experimental work. I intend to hold it there until we have more tests and > have all the pending patches merged. > > About creating an -hg tree for Siano (and for other developers), I had to nack > it in the past, since the LinuxTV server were overloaded. Now that the machine > got replaced, I think we may actually create a tree for them. > > Uri, please discuss about this in priv with me, in order to exchange the needed > information for the login account. > > > > Cheers, > Mauro Mauro, If I recall, a ton of patches were sent to the mailing list, but there was never a test tree on linuxtv.org. Were you expecting interested parties to hand-apply all those patches? It's not clear to me why you are putting this code that is untested by the community into the v4l-dvb tree. In all other cases where linuxtv developers want to submit large sets of changes, you expect them to create a private tree so testers can be solicited *before* it goes into v4l-dvb. Why would this case be any different? You have no personal knowledge as to whether the code actually works, and there are parties who have expressed a very clear concern about some of the patches causing regressions in existing hardware. Doesn't the safer approach seem to be to setup a ~mchehab/siano-patches tree so that people can do some testing, and *then* merge to the mainline? If everything works, then great - it's one command to merge the fold the tree back into the mainline... Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
