see...
-J
--
-- Forwarded message --
Date: Mon, 20 Oct 2003 10:12:19 -0500
From: "Whippo, Ryan K" <[EMAIL PROTECTED]>
To: Joshua Hoblitt <[EMAIL PROTECTED]>, Daisuke Maki <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: please remove me from list
Please remove me from list
On Mon, 20 Oct 2003, Dave Rolsky wrote:
> On Mon, 20 Oct 2003, Joshua Hoblitt wrote:
>
> > On Mon, 20 Oct 2003, Whippo, Ryan K wrote:
> >
> > > Please remove me from list
>
> Why did you resend this to him? No need to harass him.
Because he sent it another message. I responded with your origina
On Mon, 20 Oct 2003, Joshua Hoblitt wrote:
> On Mon, 20 Oct 2003, Whippo, Ryan K wrote:
>
> > Please remove me from list
Why did you resend this to him? No need to harass him.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Mon, 20 Oct 2003, Whippo, Ryan K wrote:
> Please remove me from list
>
>
--
>From [EMAIL PROTECTED] Mon Oct 20 10:51:26 2003
Date: Thu, 16 Oct 2003 19:49:00 -0500 (CDT)
From: Dave Rolsky <[EMAIL PROTECTED]>
To: "Whippo, Ryan K" <[EMAIL PROTECTED]>
Cc: DateTime <[EMAIL PROTECTED]>
Subject: RE:
Dave Rolsky wrote:
> Not using nanoseconds or leap seconds is quite intentional. Since the
> calculated values that DT::TZ uses also don't use leap second, it works
> out fine.
Yeah, but:
> On Mon, 20 Oct 2003, Flavio S. Glock wrote:
> > DateTime::TimeZone should calculate this value from
> > ut
On Mon, 20 Oct 2003, Flavio S. Glock wrote:
> RFC: deprecate DateTime.pm *_rd_as_seconds
>
> utc_rd_as_seconds
>
> - used internally. DateTime::TimeZone should calculate this value from
> utc_rd_values(), for compatibility with other calendars.
> - does not use nanoseconds or leap seconds
Not
RFC: deprecate DateTime.pm *_rd_as_seconds
utc_rd_as_seconds
- used internally. DateTime::TimeZone should calculate this value from
utc_rd_values(), for compatibility with other calendars.
- does not use nanoseconds or leap seconds
local_rd_as_seconds
- it looks like it was never used
-
