Author: sijskes
Date: Tue Nov 9 12:34:42 2010
New Revision: 1032966
URL: http://svn.apache.org/viewvc?rev=1032966&view=rev
Log:
fixed inline code fragment
Modified:
incubator/river/site/trunk/content/found-a-bug.mdtext
Modified: incubator/river/site/trunk/content/found-a-bug.mdtext
URL:
http://svn.apache.org/viewvc/incubator/river/site/trunk/content/found-a-bug.mdtext?rev=1032966&r1=1032965&r2=1032966&view=diff
==============================================================================
--- incubator/river/site/trunk/content/found-a-bug.mdtext (original)
+++ incubator/river/site/trunk/content/found-a-bug.mdtext Tue Nov 9 12:34:42
2010
@@ -7,7 +7,7 @@ Title: Found a Bug
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
[JIRA](http://issues.apache.org/jira/browse/RIVER)). 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 [Mailing
Lists](mailing-lists.html)) before adding it directly in JIRA.
-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 > fix-for-my-bug.patch}} to
generate a patch file.
+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 > fix-for-my-bug.patch` to generate
a patch file.
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.
