diff --git a/doc/C/evolution-faq.sgml b/doc/C/evolution-faq.sgml
index 184c1fa436..1f784061de 100644
--- a/doc/C/evolution-faq.sgml
+++ b/doc/C/evolution-faq.sgml
@@ -815,32 +815,20 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/
- You should report bugs about Evolution into the Ximian bug
- reporting system (Bugzilla), located at
- http://bugzilla.ximian.com.
+ You can use the GNOME Bug Report Tool
+ (bug-buddy), or report bugs to the
+ Ximian bug reporting system (Bugzilla), located at http://bugzilla.ximian.com.
Please use the query function to check if a bug has been
- submitted already before submitting it.
+ submitted already, so that we avoid duplicate reports.
-
-
-
- Can I just use Bug-Buddy?
-
-
-
-
- Not yet. The Ximian bug tracker does not yet have an
- email-based interface, so Bug Buddy cannot talk to it. This
- will be fixed eventually.
-
-
-
+
@@ -856,10 +844,10 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/
code that happened and why. For this reason, stack
traces are extremely useful for the Evolution
developers, so it's important that you learn how to get
- them, and include them in crash reports. Once we have
- bug-buddy working with our
- bug database, it will be much easier to do this. Until
- then, here's how:
+ them, and include them in crash reports. The
+ bug-buddy tool can get and
+ submit a stack trace for you. If you want to do it by
+ yourself, here's how:
First of all, in order to get a stack trace, your
@@ -939,6 +927,11 @@ bt
PID where PID is the process ID of the
component you want to debug.
+
+ If that sounds too complicated, you can always use
+ bug-buddy to get and submit the stack
+ trace.
+
@@ -946,3 +939,4 @@ bt
+
diff --git a/doc/ChangeLog b/doc/ChangeLog
index ced39c728e..4d2b84376e 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2001-06-25 Aaron Weber
+
+ * C/evolution-faq.sgml: Now that bug-buddy works with our
+ bugzilla, update faq to reflect it.
+
2001-06-25 Kevin Breit
* C/usage-mail.sgml: Put config-encryption in usage-mail.sgml. config-encryption.sgml should be depreciated.
@@ -126,10 +131,14 @@
* C/usage-mail.sgml: Updated Bcc: example
+2001-06-19 Aaron Weber
+
+ * C/usage-mainwindow.sgml: A couple changes to Kevin's update.
+
2001-06-19 Kevin Breit
* C/usage-mail.sgml: Basic edits
-
+
2001-06-19 Kevin Breit
* C/usage-exec-summary: Updated to say "My Evolution"
diff --git a/help/C/evolution-faq.sgml b/help/C/evolution-faq.sgml
index 184c1fa436..1f784061de 100644
--- a/help/C/evolution-faq.sgml
+++ b/help/C/evolution-faq.sgml
@@ -815,32 +815,20 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/
- You should report bugs about Evolution into the Ximian bug
- reporting system (Bugzilla), located at
- http://bugzilla.ximian.com.
+ You can use the GNOME Bug Report Tool
+ (bug-buddy), or report bugs to the
+ Ximian bug reporting system (Bugzilla), located at http://bugzilla.ximian.com.
Please use the query function to check if a bug has been
- submitted already before submitting it.
+ submitted already, so that we avoid duplicate reports.
-
-
-
- Can I just use Bug-Buddy?
-
-
-
-
- Not yet. The Ximian bug tracker does not yet have an
- email-based interface, so Bug Buddy cannot talk to it. This
- will be fixed eventually.
-
-
-
+
@@ -856,10 +844,10 @@ cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/
code that happened and why. For this reason, stack
traces are extremely useful for the Evolution
developers, so it's important that you learn how to get
- them, and include them in crash reports. Once we have
- bug-buddy working with our
- bug database, it will be much easier to do this. Until
- then, here's how:
+ them, and include them in crash reports. The
+ bug-buddy tool can get and
+ submit a stack trace for you. If you want to do it by
+ yourself, here's how:
First of all, in order to get a stack trace, your
@@ -939,6 +927,11 @@ bt
PID where PID is the process ID of the
component you want to debug.
+
+ If that sounds too complicated, you can always use
+ bug-buddy to get and submit the stack
+ trace.
+
@@ -946,3 +939,4 @@ bt
+
diff --git a/help/ChangeLog b/help/ChangeLog
index ced39c728e..4d2b84376e 100644
--- a/help/ChangeLog
+++ b/help/ChangeLog
@@ -1,3 +1,8 @@
+2001-06-25 Aaron Weber
+
+ * C/evolution-faq.sgml: Now that bug-buddy works with our
+ bugzilla, update faq to reflect it.
+
2001-06-25 Kevin Breit
* C/usage-mail.sgml: Put config-encryption in usage-mail.sgml. config-encryption.sgml should be depreciated.
@@ -126,10 +131,14 @@
* C/usage-mail.sgml: Updated Bcc: example
+2001-06-19 Aaron Weber
+
+ * C/usage-mainwindow.sgml: A couple changes to Kevin's update.
+
2001-06-19 Kevin Breit
* C/usage-mail.sgml: Basic edits
-
+
2001-06-19 Kevin Breit
* C/usage-exec-summary: Updated to say "My Evolution"