I have seen someone including new files in a patch, I think the person who provided the GnuArmPatch did it like that. So for those files hardly any "-" lines, and all "+" lines.
Oh please don't use third-party tools for making patches when you don't need to (and you
do not need to).
I don't know about GnuArmPatch, but we had people make patches with a diversity of Windows tools in the past. If you send in a patch that is not 100% conforming to what Subversion expects, it is a real pain. The developer reviewing/applying the patch has to gather all patched files manually and has to copy and paste every single line and remove the line header by hand.
I did that for a while, but I won't any longer. Applying an "average size" patch takes 10-15 minutes that way, and a larger patch is entirely unfeasonable. Occasionally, you use a wrong revision or confuse
+ and
- lines, too...
Reviewing and applying a conforming patch using TortoiseMerge is a matter of a few seconds (unless you changed the whole file, for example by using the source formatter). It is very straightforward to watch the changes, it works seamlessly over different releases with merges and conflicts, and you can save and apply the changes directly from the merge tool without ever having to worry about a single detail.
If you send in a patch then please use either "Create Patch..." in TortoiseSVN or a similar tool, or use the svn commandline client:
svn diff > nameofpatch.patchRegarding the question of how to make a patch for new files, this is easy. Simply
add the files to the working copy before creating the patch ("Add..." using TortoiseSVN or
svn add filename(s) using the commandline tool).
This will create
one patch file that contains all necessary data, including correct revision information.