Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@cs.uni-dortmund.de (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: vCalendar/iCalendar support for Gnus?
Date: 03 Jan 2001 18:55:05 +0100	[thread overview]
Message-ID: <vaf1yukfrly.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m33df0ftd1.fsf@sebold.lcms.org>

On 03 Jan 2001, Charles Sebold wrote:

> That said, I haven't seen the need in my own work to automate my own
> schedule that completely.  And if it ever did become so overwhelming
> that I could no longer figure out when I was free for a meeting, or
> send someone a copy of my to-do list...well, I should think my
> employer could pay for a secretary for me then.

I think the idea is that you can see other people's schedules.  And if
you want to meet with four other people, an automatic intersection of
all free times might be nice.  Of course, if you would overlay the
five schedules on top of each other, you could also see at a glance
when there are time slots that are free for everybody.

Just my two cents,
kai
-- 
~/.signature



  reply	other threads:[~2001-01-03 17:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02 15:24 Hannu Koivisto
2001-01-03 10:31 ` Kevin A. Burton
2001-01-03 17:17   ` Charles Sebold
2001-01-03 17:55     ` Kai Großjohann [this message]
2001-01-03 18:14       ` Charles Sebold
2001-01-27  5:55         ` Amos Gouaux
2001-01-03 13:50 ` Jaap-Henk Hoepman
2001-01-03 15:01   ` Hannu Koivisto
2001-01-03 16:48     ` Chris Shenton
2001-01-04  4:20     ` ShengHuo ZHU
2001-01-09 16:58     ` Paul Jarc
2001-01-09 17:03       ` ShengHuo ZHU
2001-01-03 15:47   ` Kai Großjohann
2001-01-03 16:23     ` William M. Perry
2001-01-03 16:44       ` Hannu Koivisto
2001-01-03 17:06         ` William M. Perry
2001-01-18 18:59           ` Toby Speight

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vaf1yukfrly.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).