[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Pyatcron-devel-list] CVS problem and a RFC.
From: |
NICOLOVICI Xavier |
Subject: |
RE: [Pyatcron-devel-list] CVS problem and a RFC. |
Date: |
Wed, 26 Nov 2003 17:20:12 +0100 |
Julien,
About your multiple task question, I think tht I've already sent my opinion.
Make things simple at first, we will have time later to improve or add
functionalities. For the moment, one single task = one schedule.
Xavier
> -----Message d'origine-----
> De : address@hidden
> [mailto:address@hidden
> la part de Julien Olivier
> Envoyé : mercredi, 26. novembre 2003 16:52
> À : address@hidden
> Objet : [Pyatcron-devel-list] CVS problem and a RFC.
>
>
> Hi
>
> I can't get files form the CVS today. I get the following message:
>
> cvs [server aborted]: can't chdir(/home/empty): No such file or
> directory
>
> Does anyone also have the problem ?
>
> Anyway, I'd like to work on the scheduler GUI but I'd like to know if
> you think it's a good idea to allow a Task to have more than one
> schedule. I have sent an email on the subject earlier but got
> no answer.
>
> Allowing more than one schedule per task would need to re-think the
> diagram but would enable to handle tasks which occur at multiple
> unrelated fixed dates. For example, do something on Christmas
> and on my
> birthday.
> --
> Julien Olivier <address@hidden>
>
>
> _______________________________________________
> Pyatcron-devel-list mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/pyatcron-devel-list
>
This e-mail contains proprietary information some or all of which may be
legally privileged. It is intended for the recipient only. If an addressing or
a transmission error has misdirected this e-mail, please notify the author by
replying to the e-mail. If you are not the intended recipient you must not use,
disclose, distribute, copy, print, or rely on this e-mail.
We take reasonable precautions to ensure our e-mails are virus free. However,
we cannot accept responsibility for any virus transmitted by us and recommend
that you subject any incoming e-mail to your own virus checking procedures.