https://sourceforge.net/p/text-analysis/wiki/SubmittingPatches/Recent changes to SubmittingPatchesenTue, 20 May 2014 09:36:45 -0000https://sourceforge.net/p/text-analysis/wiki/SubmittingPatches/<div class="markdown_content"><h2 id="submitting-patches">Submitting Patches</h2> <p>If you want to contribute to the core code, you must follow our <span>[ContributorLicenseAgreement]</span>. </p> <p>Before writing a patch, please, familiarize yourself with our <span>[CodingStyle]</span> conventions. </p> <p>You can create a patch using the subversion command ("<a class="" href="http://svnbook.red-bean.com/en/1.0/re09.html" rel="nofollow">svn diff &gt; ~/mypatch.diff</a>") or the unified patch format ("<a class="" href="http://en.wikipedia.org/wiki/Diff#Unified_format" rel="nofollow">diff -u</a>"). </p> <p>If you are using an eclipse svn plugin you can use the following steps: </p> <ul> <li>select the project in Package Explorer; </li> <li>right-click and select Team/Create Patch; </li> <li>select "Save In File System" and choose the file name; </li> <li>click "Next" and "Finish"; </li> <li>check unversioned resources that should be included in the patch; </li> <li>click "OK" </li> </ul> <p>Once the patch is created you should <a class="" href="https://sourceforge.net/userapps/trac/kostia76/newticket">open a ticket in Trac</a> describing the problem/bug that you solved, provide a test case if applicable, and of course attach you patch to the just created ticket. Don't mix together changes made for different reasons. Send them <strong>individually</strong>. </p></div>KostiaTue, 20 May 2014 09:36:45 -0000https://sourceforge.net95219a86395d3cec8bd436b379e2d7b89aeb4507