Thierry Merle wrote:
Hans de Goede a écrit :
I think you've misunderstood me, I would love for my v4l lib to be poart of the v4l-dvb tree as soon as the split discussed before is done, but I would like to see a mechanism to create separate tarballs for it for easy testing in the begin fase.
Regards,
Hans
Oops, sorry. You can add a rule in the makefile for that: tar: clean tar cvf /tmp/archive.tar * $(include_files_and_other_stuff_that_makes_an_independent_build)
Yes something like that should work just fine, a seen in my announcement post, I now have a split (and cleaned up) version of the code ready.
Great, I will review and try it this evening.
I would very much like this code to get included into the v4l-dvb tree, what steps are necessary for that?
Simple (refer to http://linuxtv.org/v4lwiki/index.php/How_to_submit_patches) for each part, - add the sources in the v4l-dvb tree - use hg add on all files you added - make commit, correct codestyle problems - hg export tip >patch_to_send.patch - send an email to this ML with [PATCH] in subject without forgetting the Signed-off-by line. We prefer little cumulative patches rather than a big one patch so that we are able to understand and review your code. As an example, you will see how the "old" v4l2 userspace infrastructure has been split into many patches at http://linuxtv.org/hg/~tmerle/v4l2_extension
I can help you at any step of course. I will create a separate repository to store your patches.
Thanks Thierry