aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAaron Weber <aaron@ximian.com>2001-06-26 02:43:08 +0800
committerAaron Weber <aaron@src.gnome.org>2001-06-26 02:43:08 +0800
commita5efaae60ff6a952ea754c7239c5b39c72c49ae0 (patch)
treec9c2f2f14dfa6c4ff938fdaf5459cc261c05a5f8
parent3ec4dfd27d5ffbbcfe1943252d3fbda6b4afccac (diff)
downloadgsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.tar
gsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.tar.gz
gsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.tar.bz2
gsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.tar.lz
gsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.tar.xz
gsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.tar.zst
gsoc2013-evolution-a5efaae60ff6a952ea754c7239c5b39c72c49ae0.zip
Now that bug-buddy works with our bugzilla, update faq to reflect it.
2001-06-25 Aaron Weber <aaron@ximian.com> * C/evolution-faq.sgml: Now that bug-buddy works with our bugzilla, update faq to reflect it. svn path=/trunk/; revision=10487
-rw-r--r--doc/C/evolution-faq.sgml38
-rw-r--r--doc/ChangeLog11
-rw-r--r--help/C/evolution-faq.sgml38
-rw-r--r--help/ChangeLog11
4 files changed, 52 insertions, 46 deletions
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/
</question>
<answer>
<para>
- You should report bugs about Evolution into the Ximian bug
- reporting system (Bugzilla), located at
- <ulink url="http://bugzilla.ximian.com">http://bugzilla.ximian.com</ulink>.
+ You can use the GNOME Bug Report Tool
+ (<command>bug-buddy</command>), or report bugs to the
+ Ximian bug reporting system (Bugzilla), located at <ulink
+ url="http://bugzilla.ximian.com">http://bugzilla.ximian.com</ulink>.
</para>
<para>
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.
</para>
</answer>
</qandaentry>
- <qandaentry>
- <question>
- <para>
- Can I just use Bug-Buddy?
- </para>
- </question>
- <answer>
- <para>
- 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.
- </para>
- </answer>
- </qandaentry>
+
<qandaentry>
<question>
<para>
@@ -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
- <application>bug-buddy</application> 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
+ <application>bug-buddy</application> tool can get and
+ submit a stack trace for you. If you want to do it by
+ yourself, here's how:
</para>
<para>
First of all, in order to get a stack trace, your
@@ -939,6 +927,11 @@ bt
PID</userinput> where PID is the process ID of the
component you want to debug.
</para>
+ <para>
+ If that sounds too complicated, you can always use
+ <command>bug-buddy</command> to get and submit the stack
+ trace.
+ </para>
</answer>
</qandaentry>
</qandaset>
@@ -946,3 +939,4 @@ bt
</appendix>
<!-- Local Variables: --> <!-- indent-tabs-mode:nil --> <!-- End: -->
+
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 <aaron@ximian.com>
+
+ * C/evolution-faq.sgml: Now that bug-buddy works with our
+ bugzilla, update faq to reflect it.
+
2001-06-25 Kevin Breit <battery841@mediaone.net>
* 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 <aaron@ximian.com>
+
+ * C/usage-mainwindow.sgml: A couple changes to Kevin's update.
+
2001-06-19 Kevin Breit <battery841@mediaone.net>
* C/usage-mail.sgml: Basic edits
-
+
2001-06-19 Kevin Breit <battery841@mediaone.net>
* 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/
</question>
<answer>
<para>
- You should report bugs about Evolution into the Ximian bug
- reporting system (Bugzilla), located at
- <ulink url="http://bugzilla.ximian.com">http://bugzilla.ximian.com</ulink>.
+ You can use the GNOME Bug Report Tool
+ (<command>bug-buddy</command>), or report bugs to the
+ Ximian bug reporting system (Bugzilla), located at <ulink
+ url="http://bugzilla.ximian.com">http://bugzilla.ximian.com</ulink>.
</para>
<para>
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.
</para>
</answer>
</qandaentry>
- <qandaentry>
- <question>
- <para>
- Can I just use Bug-Buddy?
- </para>
- </question>
- <answer>
- <para>
- 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.
- </para>
- </answer>
- </qandaentry>
+
<qandaentry>
<question>
<para>
@@ -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
- <application>bug-buddy</application> 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
+ <application>bug-buddy</application> tool can get and
+ submit a stack trace for you. If you want to do it by
+ yourself, here's how:
</para>
<para>
First of all, in order to get a stack trace, your
@@ -939,6 +927,11 @@ bt
PID</userinput> where PID is the process ID of the
component you want to debug.
</para>
+ <para>
+ If that sounds too complicated, you can always use
+ <command>bug-buddy</command> to get and submit the stack
+ trace.
+ </para>
</answer>
</qandaentry>
</qandaset>
@@ -946,3 +939,4 @@ bt
</appendix>
<!-- Local Variables: --> <!-- indent-tabs-mode:nil --> <!-- End: -->
+
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 <aaron@ximian.com>
+
+ * C/evolution-faq.sgml: Now that bug-buddy works with our
+ bugzilla, update faq to reflect it.
+
2001-06-25 Kevin Breit <battery841@mediaone.net>
* 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 <aaron@ximian.com>
+
+ * C/usage-mainwindow.sgml: A couple changes to Kevin's update.
+
2001-06-19 Kevin Breit <battery841@mediaone.net>
* C/usage-mail.sgml: Basic edits
-
+
2001-06-19 Kevin Breit <battery841@mediaone.net>
* C/usage-exec-summary: Updated to say "My Evolution"