From 9dcc29ab9f5223f496e70cf344c1ce710bc94c1e Mon Sep 17 00:00:00 2001 From: Mauro Carvalho Chehab Date: Sat, 11 Jun 2005 12:50:55 +0000 Subject: README.patches now reflects current policy for submiting patches. --- v4l/README.patches | 68 ++++++++++++++++++++++++++++-------------------------- 1 file changed, 35 insertions(+), 33 deletions(-) (limited to 'v4l/README.patches') diff --git a/v4l/README.patches b/v4l/README.patches index f429749b1..c1af1bf76 100644 --- a/v4l/README.patches +++ b/v4l/README.patches @@ -1,45 +1,47 @@ - April 2005 - Hi folks, +Mauro Carvalho Chehab 10 June 2005 -As you may have noticed on lkml and the v4l mailing list, I've stopped -maintaining video4linux in the linux kernels. That means: +The master copy of the video4linux kernel subsystem is now maintained at +http://www.linuxtv.org/downloads/video4linux/ - * The cvs tree at cvs.bytesex.org is *not* the "master copy" of the - video4linux subsystem any more. For the time being it is the 2.6 - standard kernel. This may change if someone else decides to take - over maintainance and handle it differently ... +=== Video4linux snapshots available from linuxtv.org === - * Patches should be built against the latest 2.6 kernel, not - against video4linux cvs. - * I've accumulated a number of v4l patches in my inbox last month, - didn't managed to process a single one of them so far due to - limited time, and I suspect this isn't going to change in the - future ... +We are now publishing periodic snapshots (about once a month) at +linuxtv.org. The main idea is to have "stable" snapshots on Linuxtv. You +can check it at: -How to get your changes into the mainline tree? + http://www.linuxtv.org/downloads/video4linux/ - (1) Post your patches to the video4linux mailing list[1] for - review and testing by other people. Fix problems and - repeat until everyone is happy ;) +The ChangeLog is also maintained at linuxtv.org. Our intention is to have +one snapshot generated at the same time it is being submited to -mm +series. - (2) Create a nice patch with changelog and everything, have - a look at the Documentation/SubmittingPatches guidelines - for the details. Make sure the patch applies fine against - the latest kernel (prefearable the latest -mm kernel). +I intend to send a first series of synchronizing patches to -mm this +weekend. There is already a working first patch at the site. - (3) Submit the patch. Mail it to the kernel mailing list[2] - and Andrew Morton[3] (the guy maintaining the -mm tree). - It's fine to Cc: me here, that probably makes it easier - to get the changes accepted because I can comment in case - there are questions or objections from Andrew or other - guys on the kernel list. +* The cvs tree at cvs.linuxtv.org is now the "master copy" of the +video4linux subsystem. -cheers, +* Patches should be built against video4linux cvs. - Gerd +===How to get your changes into the mainline tree?=== -[1] https://www.redhat.com/mailman/listinfo/video4linux-list -[2] linux-kernel@vger.kernel.org -[3] Andrew Morton +1. Post your patches to the video4linux mailing list[1] for review and +testing by other people. +2. Using [PATCH] at subject will help CVS maintainers to better handing +it. + +3. Please edit also ChangeLog, including some comments about it. + +4. Every patch should have a line like '''Signed-off-by: Your name +''' with name of people envolving on making it. + +5. Fix problems and repeat until everyone is happy ;) + +6. Maintainers will periodically submit changes to mainstream. + + +Mauro + +Mauro Carvalho Chehab -- cgit v1.2.3