summaryrefslogtreecommitdiff
path: root/mate-user-guide/C
diff options
context:
space:
mode:
authorMohammad Abu Sakib <[email protected]>2019-04-10 00:11:04 +0600
committerGitHub <[email protected]>2019-04-10 00:11:04 +0600
commit371307cfffe9e35c8f45dd5fabfc07f260209078 (patch)
tree0af9a379e02c085a683a3b9ea0353e6db6439eac /mate-user-guide/C
parent836bbc9581d680d62177988cf71cb05a5e036d22 (diff)
parent53bfda9391b7552c4c1832f962c5de2adaa6b3fb (diff)
downloadmate-user-guide-371307cfffe9e35c8f45dd5fabfc07f260209078.tar.bz2
mate-user-guide-371307cfffe9e35c8f45dd5fabfc07f260209078.tar.xz
Merge pull request #29 from selectiveduplicate/update-fback-section
update reporting-bugs section
Diffstat (limited to 'mate-user-guide/C')
-rw-r--r--mate-user-guide/C/gosfeedback.xml13
1 files changed, 4 insertions, 9 deletions
diff --git a/mate-user-guide/C/gosfeedback.xml b/mate-user-guide/C/gosfeedback.xml
index a78afba..3d08dc2 100644
--- a/mate-user-guide/C/gosfeedback.xml
+++ b/mate-user-guide/C/gosfeedback.xml
@@ -17,14 +17,11 @@
describing the circumstances under which the bug shows (What
commands did you enter? Which buttons did you click?). If there were any
error messages, be sure to include them, too.
- </para>
- <para>
- The easiest way to report bugs is by using <application>Bug Buddy</application>, MATE's built-in bug reporting tool. This will launch automatically in the event that an application crashes. The details MATE developers need are automatically collected, but you can further help by giving information about what you were doing when the crash took place.
</para>
+
<para>
- You can also submit bugs and browse the list of known bugs by
- connecting to the <link xlink:href="https://github.com/mate-desktop/">MATE bug tracking
- database</link>. You will need to register before you can submit any bugs this way.
+ The easiest way to report bugs is by connecting to the <link xlink:href="https://github.com/mate-desktop/">MATE bug tracking
+ database</link>, where you can also browse the list of known bugs. You will need to register before you can submit any bugs this way.
</para>
<para>
@@ -33,9 +30,7 @@
software). For example, <application>blueman</application>, a
bluetooth application, is developed at <link xlink:href="https://github.com/blueman-project/blueman/">GitHub</link>. Bug reports and
comments about these products should be directed to the
- respective organization or company. If you are using <application>Bug
- Buddy</application>, it will automatically send bug reports to
- the correct database.
+ respective organization or company.
</para>
</section>