HOWTO Patch - Revision history

VortexCortex: Removed 1st 'c' from "/patch/to/patchfile.patch"... too many "patch"es

2010-02-05T12:29:12Z

Removed 1st 'c' from "/patch/to/patchfile.patch"... too many "patch"es

Timothy Vollmer at 18:15, 8 June 2007

2007-06-08T18:15:59Z

Jon Phillips: added updates

2006-04-26T21:57:04Z

added updates

Jon Phillips: fleshed out

2006-04-26T21:52:47Z

fleshed out

New page

[[Category:Developer]]
[[Category:howto]]

In computing, a patch is a small piece of software designed to update or fix problems with a computer program. This includes fixing bugs, replacing graphics and improving the usability or performance. Though meant to fix problems, badly designed patches can sometimes introduce new problems. [http://en.wikipedia.org/wiki/Patch_%28computing%29]

''The general rule for Creative Commons development is for a developer to submit one good patch before getting access to the sourceforge.net project and unrestricted access to SVN. So, please submit a great patch, we will help you with formatting it properly, and then afterwards, we will give you proper access to the development trees.''

== HOWTO Create a Patch ==

You need to use a program called diff on most computers to compare the changes from one or more files against another set of one or more files. From this, one gets diff output.

The best is to create patches against the most current development version. This is done like this inside the checked out module from SVN:

<pre>
svn diff > /path/to/patchfile.patch
</pre>

For an individual file:

<pre>
svn diff changedfilename > /path/to/patchfile.patch
</pre>

=== Non SVN way to Patch ===

For the entire checked out module:

<pre>
diff -up oldfile newfile > /path/to/patchfile.patch
</pre>

== HOWTO Apply a Patch ==

<pre>
patch /path/to/file /patch/to/patchfile.patch
</pre>

== HOWTO Submit a Patch ==

Go to the [http://sourceforge.net/tracker/?group_id=80503&atid=559968 cctools Sourceforge.net path page], and then [http://sourceforge.net/tracker/?group_id=80503&atid=559968 submit your patch along with comments].

Here is [http://sourceforge.net/docman/display_doc.php?docid=24202&group_id=1#patches help with sourceforge.net's patch system].

== External Links ==

* [http://www.gimp.org/bugs/howtos/submit-patch.html Gimp pages on howto create a patch]

@@ Line 33: / Line 33: @@
 <pre>
-patch /path/to/file /patch/to/patchfile.patch
+patch /path/to/file /path/to/patchfile.patch
 </pre>

← Older revision		Revision as of 21:57, 26 April 2006
Line 37:		Line 37:

	== HOWTO Submit a Patch ==		== HOWTO Submit a Patch ==
		+
		+	Before submitting:
		+
		+	# Make sure that your code works and test and retest
		+	# Check over the patch and make sure it includes code you intended
		+	# (OPTIONAL) Re-check out the module you want to make changes to, apply your patch, and then make sure it all work.

	Go to the [http://sourceforge.net/tracker/?group_id=80503&atid=559968 cctools Sourceforge.net path page], and then [http://sourceforge.net/tracker/?group_id=80503&atid=559968 submit your patch along with comments].		Go to the [http://sourceforge.net/tracker/?group_id=80503&atid=559968 cctools Sourceforge.net path page], and then [http://sourceforge.net/tracker/?group_id=80503&atid=559968 submit your patch along with comments].

@@ Line 1: / Line 1: @@
 [[Category:Developer]]
-[[Category:howto]]
+[[Category:HOWTO]]
 In computing, a patch is a small piece of software designed to update or fix problems with a computer program. This includes fixing bugs, replacing graphics and improving the usability or performance. Though meant to fix problems, badly designed patches can sometimes introduce new problems. [http://en.wikipedia.org/wiki/Patch_%28computing%29]