diff options
| author | Dieter Plaetinck <dieter@plaetinck.be> | 2010-10-31 09:45:45 +0100 |
|---|---|---|
| committer | Chris Ball <cjb@laptop.org> | 2010-10-31 06:31:27 -0400 |
| commit | 66037fb14b06ab42eb37e6cc93d10c9717ce0d9e (patch) | |
| tree | cf595c2483f00ed04e3e2a1b678eb353c4676f95 | |
| parent | 3236d6c38c9197c9947aa63c2d1a28a18436837d (diff) | |
| download | bugseverywhere-66037fb14b06ab42eb37e6cc93d10c9717ce0d9e.tar.gz | |
Clarify that bugs cannot contain multi-line descriptions
| -rw-r--r-- | doc/tutorial.txt | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/tutorial.txt b/doc/tutorial.txt index 0da1de2..0154f5b 100644 --- a/doc/tutorial.txt +++ b/doc/tutorial.txt @@ -132,10 +132,11 @@ of the ``--reporter`` option to give them credit:: See ``be help new`` for more details. While the bug summary should include the appropriate keywords, it -should also be brief. You should probably add a comment immediately -giving a more elaborate explanation of the problem so that the -developer understands what you want and when the bug can be considered -fixed. +should also be brief. Unlike other bug trackers, the bug itself cannot +contain a multi-line description. So you should probably add a comment +immediately giving a more elaborate explanation of the problem so that +the developer understands what you want and when the bug can be +considered fixed. Commenting on bugs ------------------ |