[evolution] Change "mail:async-error" alerts to warnings.
- From: Matthew Barnes <mbarnes src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [evolution] Change "mail:async-error" alerts to warnings.
- Date: Fri, 25 Mar 2011 18:36:35 +0000 (UTC)
commit 88c041d2bca85ebe1d67f97c7e31873a4610b3b8
Author: Matthew Barnes <mbarnes redhat com>
Date: Fri Mar 25 14:21:57 2011 -0400
Change "mail:async-error" alerts to warnings.
Most Camel alerts are transient. Make them warnings so they time out.
mail/mail.error.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/mail/mail.error.xml b/mail/mail.error.xml
index d014e44..709b572 100644
--- a/mail/mail.error.xml
+++ b/mail/mail.error.xml
@@ -123,7 +123,7 @@ Many email systems add an Apparently-To header to messages that only have BCC re
<button stock="gtk-quit" response="GTK_RESPONSE_YES"/>
</error>
- <error id="async-error" type="error">
+ <error id="async-error" type="warning">
<!-- Translators: the {0} is replaced with an operation name, which failed.
It can be basically anything run asynchronously, like "Fetching Mail",
"Sending message" and others, mostly from mail-ops.c file. -->
@@ -131,7 +131,7 @@ Many email systems add an Apparently-To header to messages that only have BCC re
<secondary>{1}</secondary>
</error>
- <error id="async-error-nodescribe" type="error" scroll="yes">
+ <error id="async-error-nodescribe" type="warning" scroll="yes">
<_primary>Error while performing operation.</_primary>
<secondary>{0}</secondary>
</error>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]