<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.creativecommons.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=VortexCortex</id>
		<title>Creative Commons - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.creativecommons.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=VortexCortex"/>
		<link rel="alternate" type="text/html" href="https://wiki.creativecommons.org/wiki/Special:Contributions/VortexCortex"/>
		<updated>2026-04-17T18:04:50Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://wiki.creativecommons.org/index.php?title=HOWTO_Patch&amp;diff=28679</id>
		<title>HOWTO Patch</title>
		<link rel="alternate" type="text/html" href="https://wiki.creativecommons.org/index.php?title=HOWTO_Patch&amp;diff=28679"/>
				<updated>2010-02-05T12:29:12Z</updated>
		
		<summary type="html">&lt;p&gt;VortexCortex: Removed 1st 'c' from &amp;quot;/patch/to/patchfile.patch&amp;quot;... too many &amp;quot;patch&amp;quot;es&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Developer]]&lt;br /&gt;
[[Category:HOWTO]]&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
== HOWTO Create a Patch ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The best is to create patches against the most current development version. This is done like this inside the checked out module from SVN:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
svn diff &amp;gt; /path/to/patchfile.patch&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For an individual file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
svn diff changedfilename &amp;gt; /path/to/patchfile.patch&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Non SVN way to Patch ===&lt;br /&gt;
&lt;br /&gt;
For the entire checked out module:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
diff -up oldfile newfile &amp;gt; /path/to/patchfile.patch&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== HOWTO Apply a Patch ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
patch /path/to/file /path/to/patchfile.patch&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== HOWTO Submit a Patch ==&lt;br /&gt;
&lt;br /&gt;
Before submitting:&lt;br /&gt;
&lt;br /&gt;
# Make sure that your code works and test and retest&lt;br /&gt;
# Check over the patch and make sure it includes code you intended&lt;br /&gt;
# (OPTIONAL) Re-check out the module you want to make changes to, apply your patch, and then make sure it all work.&lt;br /&gt;
&lt;br /&gt;
Go to the [http://sourceforge.net/tracker/?group_id=80503&amp;amp;atid=559968 cctools Sourceforge.net path page], and then [http://sourceforge.net/tracker/?group_id=80503&amp;amp;atid=559968 submit your patch along with comments].&lt;br /&gt;
&lt;br /&gt;
Here is [http://sourceforge.net/docman/display_doc.php?docid=24202&amp;amp;group_id=1#patches help with sourceforge.net's patch system].&lt;br /&gt;
&lt;br /&gt;
== External Links ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.gimp.org/bugs/howtos/submit-patch.html Gimp pages on howto create a patch]&lt;/div&gt;</summary>
		<author><name>VortexCortex</name></author>	</entry>

	</feed>