On Tue, 2011-02-22 at 11:30 +1300, Andrew McMillan wrote:
> [...]
> Hi Carlos,
>
> From RFC5545:
>
> The INTERVAL rule part contains a positive integer representing at
> which intervals the recurrence rule repeats. The default value is
> "1", meaning every second for a SECONDLY
On Mon, 2011-02-21 at 14:08 +0100, Carlos Martín Nieto wrote:
> On Thu, 2011-02-17 at 08:21 +0100, Milan Crha wrote:
> > On Thu, 2011-02-17 at 00:48 +0100, Carlos Martín Nieto wrote:
> > > I've attached the backtrace for a year of 167 (I think) though I don't
> > > think it gives much information.
On Thu, 2011-02-17 at 08:21 +0100, Milan Crha wrote:
> On Thu, 2011-02-17 at 00:48 +0100, Carlos Martín Nieto wrote:
> > I've attached the backtrace for a year of 167 (I think) though I don't
> > think it gives much information. This happens even if I have my main
> > calendar off (which I think i
On Thu, 2011-02-17 at 00:48 +0100, Carlos Martín Nieto wrote:
> I've attached the backtrace for a year of 167 (I think) though I don't
> think it gives much information. This happens even if I have my main
> calendar off (which I think it's the only one with recurring events).
Hi,
this is
Hi all,
I'm running evo master, and I've been getting weird messages, about the
year being below 1900 (the assert in libecal's time_days_in_month().
I've put a g_print() statement to print the year on each run. The
messages scroll too fast for me to see each one, but I could see the
years countin
