<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link rel="home" title="HomePage" href="HomePage.html" />
<link rel="help" title="HowToUseWiki" href="HowToUseWiki.html" />
<link rel="copyright" title="GNU General Public License" href="http://www.gnu.org/copyleft/gpl.html#SEC1" />
<link rel="author" title="The PhpWiki Programming Team" href="http://phpwiki.org/ThePhpWikiProgrammingTeam" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta http-equiv="Content-Language" content="en" />
<meta name="robots" content="noindex,nofollow" />
<meta name="language" content="en" />
<meta name="document-type" content="Public" />
<meta name="document-rating" content="General" />
<meta name="generator" content="PhpWiki" />
<meta name="PHPWIKI_VERSION" content="1.3.14" />

<link rel="stylesheet" type="text/css" charset="iso-8859-1" href="phpwiki-printer.css" />
<title>PhpWiki - Submitting Patches</title>
</head>
<body>

<div id="header">
  
<!-- Page title -->
<h1>Submitting Patches</h1>
</div>
<div id="content">



<div class="wikitext"><p class="tightenable top">The process described here will maximize the chance that your patch will be included in the mainstream codeline.</p>
<dl><dt class="tightenable">The best way to make your contribution is to</dt>
<dd class="tightenable"><ul><li class="tightenable top">Use the <a href="http://sourceforge.net/tracker/?atid=615772&amp;group_id=96750&amp;func=browse" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />sourceforge</span> bug tracker</a> (and/or the <a href="http://bugs.contribs.org/main_page.php" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />contribs.org</span> one</a>) to open a bug report for the bug you have found.</li>
<li class="tightenable">Submit your patch into the bug report as a suggested fix.</li>
<li class="tightenable bottom">An optional third step is to go away and build an RPM containing your fix.</li>
</ul>
</dd>
</dl>
<p class="tightenable">The reason why it is not necessary to submit an RPM &amp; SRPM is that it can actually make it harder for the devs. They would need to grab your source RPM and extract the source code, then determine what version you branched from, then do a diff. It is much easier if you just describe your fix or post a patch file in the bug report.</p>
<p class="tightenable bottom">The patch can either be a code snippet for the fix, or for more complex changes an actual patch file (see <a href="http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/6.x/howto/rpm-patch-howto.html" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />patch</span> a SME Server rpm</a>) is easier to deal with.</p>
</div>

<div id="footer">  <hr class="printer" noshade="noshade" />
<p class="editdate">Owner: &quot;wellsi&quot;  Last edited on March 13, 2005  2:13 pm by &quot;wellsi&quot;</p>
</div>

</div>
<!-- Add your Disclaimer here -->
</body>
</html>
