From: Zwane Mwaikambo A kernel janitor recently got confused by the advice in SubmittingPatches and was sending patches with the wrong strip level, i think just about everyone would prefer standard patches. Also mention various patch management scripts for batching up large deltas. --- 25-akpm/Documentation/SubmittingPatches | 19 +++++++++++++++++-- 1 files changed, 17 insertions(+), 2 deletions(-) diff -puN Documentation/SubmittingPatches~submittingpatches-diffing-update Documentation/SubmittingPatches --- 25/Documentation/SubmittingPatches~submittingpatches-diffing-update 2004-04-25 21:53:16.045868136 -0700 +++ 25-akpm/Documentation/SubmittingPatches 2004-04-25 21:53:16.048867680 -0700 @@ -35,13 +35,14 @@ not in any lower subdirectory. To create a patch for a single file, it is often sufficient to do: - SRCTREE= /devel/linux-2.4 + SRCTREE= linux-2.4 MYFILE= drivers/net/mydriver.c cd $SRCTREE cp $MYFILE $MYFILE.orig vi $MYFILE # make your change - diff -up $MYFILE.orig $MYFILE > /tmp/patch + cd .. + diff -up $SRCTREE/$MYFILE{.orig,} > /tmp/patch To create a patch for multiple files, you should unpack a "vanilla", or unmodified kernel source tree, and generate a diff against your @@ -63,6 +64,20 @@ Make sure your patch does not include an belong in a patch submission. Make sure to review your patch -after- generated it with diff(1), to ensure accuracy. +If your changes produce a lot of deltas, you may want to look into +splitting them into individual patches which modify things in +logical stages, this will facilitate easier reviewing by other +kernel developers, very important if you want your patch accepted. +There are a number of scripts which can aid in this; + +Quilt: +http://savannah.nongnu.org/projects/quilt + +Randy Dunlap's patch scripts: +http://developer.osdl.org/rddunlap/scripts/patching-scripts.tgz + +Andrew Morton's patch scripts: +http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.16 2) Describe your changes. _