wiki : create "Creating patches" page

[mmadia]

Such a page would instruct users the preferred way to create patches.

Create one designed to be sent upstream for check-in, create a second that contains non-desirable or temporary work-arounds to be stored locally.

Mention preferred usage of diff, which includes flags such as -Naur, where diff should be run: top-level package folder or its parent? how directories should be set up for non-version controlled software.

This would help to ensure uniformity between individual porters.

[brecht]

There is already such a page (CreatePatch). Unfortunately, just like many other wiki pages, the content is badly in need of an update. This page should also include information on how to create patches using version control software.

[mmadia]

I've added a blurb to CreatePatch on how to create patches using subversion. Mentions the typical preference for submitting patches for software maintainers and BePorter?'s (current) preference.

[scottmc]

I've updated the CreatePatch page to hopefully better explain how to make a patch, how to check it and where to put it. One of the key things I found was that haikuporter needs the patches placed into a "patches" folder. Just putting them into the same folder as the .bep file doesn't work. Perhaps haikuporter should be changed to find them in either place? Seeing as the patch file need to have the same name as the .bep file except for the extension it shouldn't get in the way I'd think.