Control Creation Paths

-nopatch="filename with spaces"
-nopatch=pattern

Forbid GenPatch to use patching for this file. If the file was changed, this means it will have to be included in complete into the patch file. This ensures that the patch will create the file successfully without imposing any requirement. You loose the patching efficiency though and so this may only be a way to go with relatively small files. Consider  -unimportant if you are just interested to make a file imposing no requirement for the overall success of applying the patch file.

-force="filename with spaces"
-force=pattern
-force
-f

The first two forms are for use in directory mode only. They will force that files matching the filename must be produced by the patch file even if they are present identical in all start states. If you use -nopatch additionally the file will be included in complete. If you do not, the patch will produce the file by copying an existing identical file of the same version. The plain form "-force"  will be the same as "-f=*" with directories and for files it will force creating patch files of identical files or such this that do not match well.

-exact="filename with spaces"
-exact=pattern
-e=pattern
-e

This option makes sense in directory mode only. It will force that only filenames with exactly the same filename are considered when it comes to selecting how to produce a file in the end state. You disable auto-detection for the file using this option. If no file with the same name is present, the effect is the same as -nopatch since when no creation path is found, GenPatch must include the file without producing it by patching.