Le dimanche 12 mars 2006 à 19:19 +0100, Hans Verkuil a écrit :
> I have a life outside ivtv 
> you know. And, as I've said above, most of the effort is simply not 
> visible on the ivtv mailinglists. Just check the changelogs in the 
> 2.6.15 and 2.6.16 kernels to see what I've contributed there.

Hans,

Thank you for your answer. I came out a bit harsher than I intended.

I know there is a steady ivtv -> v4l -> vanilla code flow
I guess what I don't understand is why you don't release ivtv patchsets
that work on a vanilla kernel (since as you wrote they do include your
changes after a short merge time period)

That would massively simplify the work of third-parties like me.
Of course that would also mean stuff depending on v4l bits not merged
yet wouldn't be available before the merge. But (and here maybe I'm
wrong again) the v4l -> linus merge time does not seem the limiting
factor right now.

-- 
Nicolas Mailhot

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to