tiOPF Code Submission guidelines

To stand a greater chance of having your patch successfully submitted to the SubVersion repository, the follow list of rules needs to be followed.

Make sure you have the latest revisions of the files just before you create a patch.
Type: svn up
Make sure there are no conflicts and that everything compiles.
Confirm you are using the latest SVN conf file, which can be found here:

http://tiopf.svn.sourceforge.net/viewvc/*checkout*/tiopf/tiOPF2/Trunk/SVNConfig.txt

This will ensure line endings are compatible with Windows and Linux. Important!
Write unit tests for new feature you added. Important!
Run all the unit tests to make sure you broke nothing. Important!
Write help text in PasDoc format embedded in the source.
Create a patch. You can keep the unit test changes separate or give it all as one single patch file. A single patch file must contain everything needed for something to work. One patch file cannot rely on another patch file's changes. Create the patch as follows:
```
  cd <tiopf>/Source       <== tiOPF2/Trunk
  svn diff > MyPatchName.patch
```
If you are not sure about the syntax, type: svn help diff
If the patch is huge (please try not to make to many changes in a single patch), zip it up and email it to the tiopf.binary newsgroup.

Can I please emphasise the importance of (3), (4) and (5)