aboutsummaryrefslogtreecommitdiffstats
path: root/help/C
diff options
context:
space:
mode:
authorAndre Klapper <a9016009@gmx.de>2011-08-19 21:29:51 +0800
committerAndre Klapper <a9016009@gmx.de>2011-08-19 21:29:51 +0800
commit9ace73c689000530715aafb47398253ad82d16fe (patch)
tree7e4cfca98bd4a590cfb03e13b5aaee931c05e4dc /help/C
parent6b13cb5be7462b7e6e43af07e6051a553fb5d127 (diff)
downloadgsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.tar
gsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.tar.gz
gsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.tar.bz2
gsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.tar.lz
gsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.tar.xz
gsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.tar.zst
gsoc2013-evolution-9ace73c689000530715aafb47398253ad82d16fe.zip
Update user doc instructions now that UI bug 655494 is fixed
Diffstat (limited to 'help/C')
-rw-r--r--help/C/calendar-free-busy.page4
-rw-r--r--help/C/calendar-meetings-replying-to-invitation.page7
2 files changed, 3 insertions, 8 deletions
diff --git a/help/C/calendar-free-busy.page b/help/C/calendar-free-busy.page
index 6eb4f19d39..0c1f7392fe 100644
--- a/help/C/calendar-free-busy.page
+++ b/help/C/calendar-free-busy.page
@@ -6,7 +6,7 @@
<link type="guide" xref="calendar-sharing-information" />
- <revision pkgversion="3.0.2" version="0.2" date="2011-07-31" status="final"/>
+ <revision pkgversion="3.1.5" version="0.3" date="2011-08-19" status="final"/>
<credit type="author">
<name>Andre Klapper</name>
<email>ak-47@gmx.net</email>
@@ -24,8 +24,6 @@
<p>You can use the Free/Busy search for meetings to determine the availability of invitees.</p>
-<!-- TODO: Recheck once https://bugzilla.gnome.org/show_bug.cgi?id=655494 is fixed -->
-
<p>In addition to the standard meeting scheduling tools, you can use the Free/Busy view to check whether people are available in advance. The Free/Busy feature is normally a function of dedicated groupware servers such as Microsoft Exchange and Novell GroupWise. However, you can also publish Free/Busy information online, and access Free/Busy information published elsewhere. If not everyone you collaborate with publishes Free/Busy data, you can still use <link xref="calendar-meetings-sending-invitation">meeting invitations</link> to coordinate schedules with other people.</p>
<p>To access the free/busy view:</p>
diff --git a/help/C/calendar-meetings-replying-to-invitation.page b/help/C/calendar-meetings-replying-to-invitation.page
index 66d3e53f51..855b0d3f8c 100644
--- a/help/C/calendar-meetings-replying-to-invitation.page
+++ b/help/C/calendar-meetings-replying-to-invitation.page
@@ -6,7 +6,7 @@
<link type="guide" xref="calendar-meetings" />
- <revision pkgversion="3.0.2" version="0.3" date="2011-08-01" status="final"/>
+ <revision pkgversion="3.1.5" version="0.4" date="2011-08-19" status="final"/>
<credit type="author">
<name>Andre Klapper</name>
<email>ak-47@gmx.net</email>
@@ -18,8 +18,6 @@
<p>Creative Commons Share Alike 3.0</p>
</license>
-<!-- TODO: Check if all these steps are still correct in 3.1 -->
-
</info>
<title>Replying to a Meeting Request</title>
@@ -28,6 +26,5 @@
<p>Click <gui style="button">OK</gui> to send your answer per email to the organizer. The event is also added automatically to your calendar if you accept.</p>
<p>After you have added the meeting to your calendar, you can make changes to the meeting, but if the original organizer sends out an update, your changes might be overwritten.</p>
-<note><p>Under <guiseq><gui>Edit</gui><gui>Preferences</gui><gui>Mail Preferences</gui><gui>Calendar and Tasks</gui><gui>Conflict Search</gui></guiseq> you can define which calendars are used for warning you of meeting conflicts.</p></note>
-<!-- TODO: Recheck once https://bugzilla.gnome.org/show_bug.cgi?id=655494 is fixed -->
+<note><p>Under <guiseq><gui>Edit</gui><gui>Preferences</gui><gui>Calendar and Tasks</gui><gui>Meeting Invitations</gui><gui>Conflict Search</gui></guiseq> you can define which calendars are used for warning you of meeting conflicts.</p></note> <!-- This is the location since 3.1.5, see bug https://bugzilla.gnome.org/show_bug.cgi?id=655494 -->
</page>