How To Create Patch For Stendhal: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Madmetzger |
imported>Kymara No edit summary |
||
| Line 33: | Line 33: | ||
== Command line way == |
== Command line way == |
||
In your stendhal code development folder type: |
|||
{{TODO|describe how to create a patch via command line, for now try reading http://www.kegel.com/academy/opensource.html#patches}} |
|||
cvs diff -uN > descriptive_name.patch |
|||
If you have unversioned (new!) files to include in your patch, you will notice that the above command simply adds the file's name to the top of your patch, prefixed with a question mark. You can check this by opening the patch file in any text editor. This is because your new file is not tagged for adding to the repository. Just do |
|||
cvs add newfile |
|||
{{TODO|Verify this is possible with anon access ? }} |
|||
Then |
|||
cvs diff -uNa > descriptive_name.patch |
|||
This should add the correct code to the patch, so that someone applying the patch to their working copy will have a new file created at the right place (hopefully!). |
|||
If your patch, for some reason (like you being on Windows), contains a lot of white space changes in many files, you might want to add -Bbw to the diff call. This can make a patch a lot smaller, and thus easier to review. The complete call would then be |
|||
cvs diff -uNawbB > descriptive_name.patch |
|||