aboutsummaryrefslogtreecommitdiffstats
path: root/help/C/calendar-meetings-replying-to-invitation.page
blob: 5f0e9a99805651e5f936941c2ff7be9fa9879496 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its"
      type="topic" id="calendar-meetings-replying-to-invitation">

  <info>
    <desc>Accepting and replying to a meeting invitation.</desc>
    
    <link type="guide" xref="calendar-meetings" />

    <revision pkgversion="3.1.5" version="0.5" date="2011-08-24" status="final"/>
    <credit type="author">
      <name>Andre Klapper</name>
      <email>ak-47@gmx.net</email>
    </credit>
    <credit type="author">
 <name>Novell, Inc</name> <!-- Content partially from http://library.gnome.org/users/evolution/2.32/usage-calendar-apts.html.en#replying-to-rsvp -->
    </credit>
    <license>
      <p>Creative Commons Share Alike 3.0</p>
    </license>  

  </info>

<title>Replying to a Meeting Request</title>
<p>Meeting requests are sent as attachments. To view or respond to one, click the attachment icon and view it in the mail window. All the details about the event are shown, including time and dates. Then you can choose how to reply to the invitation - the options are to <gui>Decline</gui>, Tentatively Accept (<gui>Tentative</gui>), or <gui>Accept</gui>.</p>

<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>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>