> On Wed, 2010-08-11 at 15:16 +0200, ext Mauro Carvalho Chehab wrote: >> Em 11-08-2010 08:44, Matti J. Aaltonen escreveu: >> > Hi again. >> > >> > On Wed, 2010-08-11 at 14:34 +0300, Matti J. Aaltonen wrote: >> >> Hello. >> >> >> >> On Wed, 2010-08-11 at 12:56 +0200, ext Hans Verkuil wrote: >> >>>> Hi. >> >>>> >> >>>> I cloned your tree at http://linuxtv.org/git/media_tree.git and >> checked >> >>>> out the origin/staging/v2.6.37 branch and the >> >>>> Documentation/video4linux/v4l2-controls.txt just isn't there. I >> asked >> >>>> one of my colleagues to do the same and the result was also the >> same. >> >>> >> >>> The file is in the v2.6.36 branch. It hasn't been merged yet in the >> >>> v2.6.37 branch. >> >> >> >> 37 above was a typo, sorry. My point was that we couldn't find it in >> the >> >> origin/staging/v2.6.36 branch... and that the branch lags behind of >> what >> >> can be seen via the git web interface... >> >> >> >> B.R. >> >> Matti >> > >> > I'd suggest - if that's not too much trouble - that you'd clone the >> tree >> > using http (from http://linuxtv.org/git/media_tree.git) and then >> checked >> > out the 36 branch and see that it works for you and then post the >> > command you used and then I'll admit what I did wrong - if >> necessary:-) >> >> You should try to avoid using http method for clone/fetch. It depends on >> some >> files that are created by running "git update-server-info". There's a >> script to >> run it automatically after each push. Yet, the better is to use git. > > I guess I didn't emphasize my point enough... I would avoid using http > if it wasn't the only protocol I can use to access your site... And if > you have serious problems with it I think it would be fair to mention > that on your git web page... FYI: the control framework has been merged into the mainline, so you can get it from there as well. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco -- 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
