@@ -14,7 +14,6 @@ Please read this document before making contributions.
14
14
on how to reproduce it. If it is a compiler or language bug, please try to include a minimal
15
15
example. This means don't post all 200 lines of code from your project, but spend some time
16
16
distilling the problem to just the relevant code.
17
- * Add the ` bug ` tag to the issue.
18
17
19
18
## Contributing Changes
20
19
@@ -30,8 +29,7 @@ may require changes before being merged.
30
29
the test folder and make sure it is run when` make test ` is invoked.
31
30
* Be consistent with the style. For C this means follow the indentation and style in
32
31
other files (files have MIT license at top, 4 spaces indentation, no trailing
33
- whitespace, cuddled brackets, etc.) Use ` make format ` to
34
- automatically format your C code with
32
+ whitespace, cuddled brackets, etc.) Use ` make format ` to automatically format your C code with
35
33
[ astyle] ( http://astyle.sourceforge.net/astyle.html ) . You will probably need
36
34
to install this, but it can be installed with most package managers.
37
35
@@ -75,4 +73,3 @@ timely manner. In short, if you want extra functionality now, then build it.
75
73
76
74
* Include a good description of the problem that is being solved
77
75
* Include descriptions of potential solutions if you have some in mind.
78
- * Add the appropriate tags to the issue. For new features, add the ` enhancement ` tag.
0 commit comments