|
1 | 1 | Please read the following carefully before submitting this new issue. |
2 | 2 |
|
3 | | - - Please ensure, that you are really reporting a bug. When in doubt, |
4 | | - post a message on https://groups.google.com/forum/#!forum/libmodbus |
5 | | - or send an email to [email protected] |
| 3 | +- Please ensure, that you are really reporting a bug. When in doubt, post a |
| 4 | + message on <https://groups.google.com/forum/#!forum/libmodbus> or send an |
| 5 | + |
6 | 6 |
|
7 | | - - Please do not open issues to ask questions about using libmodbus. |
8 | | - Use the mailing list for this as there are many more people reading |
9 | | - that list, who could help you. |
| 7 | +- Please do not open issues to ask questions about using libmodbus. Use the |
| 8 | + mailing list for this as there are many more people reading that list, who |
| 9 | + could help you. |
10 | 10 |
|
11 | | - - When using libmodbus from a distribution (Debian, Fedora...), please |
12 | | - report the bug first in the bug tracker of the distribution. The |
13 | | - reason for doing so is that the package maintainer should have a chance |
14 | | - to look at the issue first as it might be a packaging error. If/when |
15 | | - the package maintainer comes to the conclusion that is really an upstream |
16 | | - bug, then he/she will usually report it here by himself/herself. |
17 | | - This is because he/she is interested in staying in the notification chain |
18 | | - to decide about a backport as soon as a bugfix is available. |
19 | | - Otherwise you (distribution user) will be asked to do so explicitely. |
| 11 | +- When using libmodbus from a distribution (Debian, Fedora...), please report |
| 12 | + the bug first in the bug tracker of the distribution. The reason for doing so |
| 13 | + is that the package maintainer should have a chance to look at the issue first |
| 14 | + as it might be a packaging error. If/when the package maintainer comes to the |
| 15 | + conclusion that is really an upstream bug, then he/she will usually report it |
| 16 | + here by himself/herself. This is because he/she is interested in staying in |
| 17 | + the notification chain to decide about a backport as soon as a bugfix is |
| 18 | + available. Otherwise you (distribution user) will be asked to do so |
| 19 | + explicitly. |
20 | 20 |
|
21 | | -When you get here and you are still convinced that you want report a bug: |
| 21 | +When you get here and you are still convinced that you want to report a bug: |
22 | 22 |
|
23 | | - - *Use a clear and decriptive title* for the issue to identify |
| 23 | +- *Use a clear and descriptive title* for the issue to identify |
24 | 24 |
|
25 | | - - *Which version of libmodbus are you using?* you can obtain this information |
| 25 | +- *Which version of libmodbus are you using?* you can obtain this information |
26 | 26 | from your package manager or by running `pkg-config --modversion libmodbus`. |
27 | 27 | You can provide the sha1 of the commit if you have fetched the code with `git`. |
28 | 28 |
|
29 | | - - *Which operating system are you using?* |
| 29 | +- *Which operating system are you using?* |
30 | 30 |
|
31 | | - - *Describe the exact steps which reproduce the problem* in as many details as |
32 | | - possible. For example, the software/equipement which runs the Modbus server, how |
| 31 | +- *Describe the exact steps which reproduce the problem* in as many details as |
| 32 | + possible. For example, the software/equipment which runs the Modbus server, how |
33 | 33 | the clients are connected (TCP, RTU, ASCII) and the source code you are using. |
34 | 34 |
|
35 | | - - *Enable the debug mode*, libmodbus provides a function to display the content |
| 35 | +- *Enable the debug mode*, libmodbus provides a function to display the content |
36 | 36 | of the Modbus messages and it's very convenient to analyze issues |
37 | | - (http://libmodbus.org/docs/latest/modbus_set_debug.html). |
| 37 | + (<http://libmodbus.org/docs/modbus_set_debug/>). |
38 | 38 |
|
39 | 39 | Good bug reports provide right and quick fixes! |
40 | 40 |
|
@@ -62,11 +62,11 @@ everything up to and including the following line which starts with ---. |
62 | 62 |
|
63 | 63 | <...> |
64 | 64 |
|
65 | | -## Expected behaviour |
| 65 | +## Actual behavior if applicable |
66 | 66 |
|
67 | 67 | <...> |
68 | 68 |
|
69 | | -## Actual behaviour |
| 69 | +## Expected behavior or suggestion |
70 | 70 |
|
71 | 71 | <...> |
72 | 72 |
|
|
0 commit comments