Make a directory that contains the source code before your edits (let's call it hijack.v200). Make a different directory at the same level that contains the source code after your edits (let's call this one hijack.v200.ta). To be clear, these two directories should be subdirectories of one parent directory, so that they are direct siblings. Make sure that you are in that parent directory so that you can see both source code directories. Now enter the command ``diff -ruN hijack.v200 hijack.v200.ta > ta.patch''. This will create a recursive unified diff that includes brand new files and write it to the file `ta.patch'. (Since it includes brand new files, the new source tree should not contain compiled object files and whatnot. It should be as pristine as possible.) (Also, for the record, mlord uses the diff command ``diff -u --recursive --new-file --exclude=zImage --exclude=config.ini --exclude=.* --exclude=*.patch --exclude=buildit --exclude=defconfig <orig> <new>''. The `--recursive' and `--new-file' options correspond to my `r' and `N' options. The rest is for his convenience and should be fairly obvious.) (Oh -- you'll have to make sure that you're using a GNU diff. If you get an error that the -u option is unknown, go download it. It's much better than anything that a more standard diff can give you.)