aboutsummaryrefslogtreecommitdiffstats
path: root/guide/ch25.html
diff options
context:
space:
mode:
Diffstat (limited to 'guide/ch25.html')
-rw-r--r--guide/ch25.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/guide/ch25.html b/guide/ch25.html
index d55e66a..983e946 100644
--- a/guide/ch25.html
+++ b/guide/ch25.html
@@ -48,7 +48,7 @@ NOW, open a ticket as previously explained.</p><p>Once you have opened a ticket,
questions in a timely manner and confirm that the bug was
indeed fixed when it is.</p><p>If you can’t be patient, either try to solve the bug and
contribute the fix back or become a paying customer.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_code_2"></a>25.3. Code</h2></div></div></div><p>The code is located in the <span class="emphasis"><em>core/*.mk</em></span> and <span class="emphasis"><em>plugins/*.mk</em></span> files.
-The tests are located in the <span class="emphasis"><em>test/Makefile</em></span> and <span class="emphasis"><em>test/\*.mk</em></span> files.</p><p>If you have a fix or a hack for a bug, you should open a
+The tests are located in the <span class="emphasis"><em>test/Makefile</em></span> and <span class="emphasis"><em>test/*.mk</em></span> files.</p><p>If you have a fix or a hack for a bug, you should open a
pull request. Any fix should include a test case that fails
before the fix and is working after.</p><p>If you have a test case that reproduces a bug, but no fix for
it, you should open a pull request.</p><p>Changes need to be tested with at least the <code class="literal">make check</code>