March 2011 Archives by date

Messages sorted by: [ thread ] [ subject ] [ author ]
More info on this list...

Starting: Tue Mar 1 09:21:09 CET 2011
Ending: Thu Mar 31 19:44:39 CEST 2011
Messages: 88

KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Till Adam
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Bernhard Reiter
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Till Adam
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Jeroen van Meeuwen (Kolab Systems)
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Bernhard Reiter
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Till Adam
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Bernhard Reiter
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Bernhard Reiter
Basic rationale of the KEP #2 design Florian v. Samson
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Florian v. Samson
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design Shawn Walker
Basic rationale of the KEP #2 design Joon Radley
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Joon Radley
Basic rationale of the KEP #2 design Joon Radley
Basic rationale of the KEP #2 design Joon Radley
Basic rationale of the KEP #2 design Florian v. Samson
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Bernhard Reiter
Kontact, Qt and RFC3339 (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
On perserving tags (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Use of the Olson database (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design Georg C. F. Greve
Use of the Olson database (Re: Basic rationale of the KEP #2 design) Joon Radley
Kontact, Qt and RFC3339 (Re: Basic rationale of the KEP #2 design) Georg C. F. Greve
Basic rationale of the KEP #2 design Bernhard Reiter
Use of the Olson database (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Basic rationale of the KEP #2 design Bernhard Reiter
KEP #2: datetime RFC3339 and ISO 8601 and requirement of tz Till Adam
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design Florian v. Samson
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design Hendrik Helwich
Cancelled: KEP #2 Closing Call Jeroen van Meeuwen (Kolab Systems)
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design Jeroen van Meeuwen (Kolab Systems)
Basic rationale of the KEP #2 design Georg C. F. Greve
Basic rationale of the KEP #2 design - Part 1 Florian v. Samson
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Florian v. Samson
Basic rationale of the KEP #2 design Jeroen van Meeuwen (Kolab Systems)
Use of TZID in invitations (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
On preserving tags (Re: Basic rationale of the KEP #2 design - Part 1) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
KEP2: format datetime format suggestion (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Florian v. Samson
Basic rationale of the KEP #2 design - Part 1 Georg C. F. Greve
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Georg C. F. Greve
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Georg C. F. Greve
Use of TZID in invitations (Re: Basic rationale of the KEP #2 design) Georg C. F. Greve
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Basic rationale of the KEP #2 design - Part 1 Bernhard Reiter
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Florian v. Samson
Why and when storing local time? Bernhard Reiter
Use of TZID in invitations (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Florian v. Samson
ISO-8601 compliance (Re: Why and when storing local time?)) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Georg C. F. Greve
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Georg C. F. Greve
Use of TZID in invitations (Re: Basic rationale of the KEP #2 design) Georg C. F. Greve
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Use of TZID in invitations (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Florian v. Samson
Use of TZID in invitations Bernhard Reiter
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Jeroen van Meeuwen (Kolab Systems)
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Florian v. Samson
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Georg C. F. Greve
A summary of sorts (was: Re: Why and when storing local time? (Re: Basic rationale of the KEP #2 design)) Georg C. F. Greve
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Florian v. Samson
A summary of sorts (was: Re: Why and when storing local time? (Re: Basic rationale of the KEP #2 design)) Florian v. Samson
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Bernhard Reiter
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Florian v. Samson
A summary of sorts (was: Re: Why and when storing local time? (Re: Basic rationale of the KEP #2 design)) Georg C. F. Greve
Rationale of the KEP2 design: central in-format TZ-data vs. individual local TZ-databases and more (Part 2) Florian v. Samson
Why and when storing local time? (Re: Basic rationale of the KEP #2 design) Florian v. Samson

Last message date: Thu Mar 31 19:44:39 CEST 2011
Archived on: Tue Jul 9 09:56:55 CEST 2013

Messages sorted by: [ thread ] [ subject ] [ author ]
More info on this list...

This archive was generated by Pipermail 0.09 (Mailman edition).