svn commit: r778967 - /websites/staging/river/trunk/content/found-a-bug.html

[bu...@apache.org]

Author: buildbot
Date: Tue Nov  9 12:34:56 2010
New Revision: 778967

URL: http://svn.apache.org/viewvc?rev=778967&view=rev
Log:
Staging update by buildbot

Modified:
    websites/staging/river/trunk/content/found-a-bug.html

Modified: websites/staging/river/trunk/content/found-a-bug.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/found-a-bug.html?rev=778967&r1=778966&r2=778967&view=diff
==============================================================================
--- websites/staging/river/trunk/content/found-a-bug.html (original)
+++ websites/staging/river/trunk/content/found-a-bug.html Tue Nov  9 12:34:56 2010
@@ -70,7 +70,7 @@
           <div class="wiki-content">
 <h1 id="found_a_bug">Found a Bug?</h1>
 <p>If you think you've found a problem with Apache River you can search JIRA, our issue-tracking system, to see if the problem has already been noted (visit <a href="http://issues.apache.org/jira/browse/RIVER">JIRA</a>). If the issue is not listed there, you can add a new JIRA issue describing it, please include detailed steps to reproduce the problem. Often it is best to raise an issue not yet listed in JIRA first on the River Developer mailing list (see <a href="mailing-lists.html">Mailing Lists</a>) before adding it directly in JIRA.</p>
-<p>If you have a fix for the issue, you can generate a patch file to send the fix to us. You need to check out the current source code from Subversion, make the necessary changes, and then do a full build. And, of course, confirm that the problem is actually fixed. Then, go to the base directory of your RIVER checkout, and run a command like {{svn diff &gt; fix-for-my-bug.patch}} to generate a patch file.</p>
+<p>If you have a fix for the issue, you can generate a patch file to send the fix to us. You need to check out the current source code from Subversion, make the necessary changes, and then do a full build. And, of course, confirm that the problem is actually fixed. Then, go to the base directory of your RIVER checkout, and run a command like <code>svn diff &gt; fix-for-my-bug.patch</code> to generate a patch file.</p>
 <p>To submit a patch, create an issue in JIRA that describes the problem, and add your patch file as an attachment. Please include detailed steps to reproduce the problem in the issue description, and a test case in the patch where possible.</p>
 <p>Thanks for interest, and working with us to improve Apache River!</p>
           </div>