linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Hanna Linder <hannal@us.ibm.com>, jw schultz <jw@pegasys.ws>
Cc: lse-tech@lists.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: LSE conference call
Date: Fri, 25 Apr 2003 13:55:03 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1030425134717.16623B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <20030423011320.GG21518@pegasys.ws>

On Tue, 22 Apr 2003, Hanna Linder wrote:

> 
> In light of our speaker sleeping through the meeting and
> the fact that kernel hackers tend not to be awake early
> in the morning I propose moving the time of the call to
> 1pm Pacific Time (GMT-0800). 
> 
> Originally we chose 9:30am to encourage people in Europe and 
> India to attend. However, the time change has not increased 
> attendance so I think we should move it to a more reasonable 
> time for North American Continental dwellers who are the 
> main attendees.
> 
> Any comments? Debate? Hate mail?

Must have been really short, I missed it coming in a tad late. In any
case, NY is nicely in the middle between CA and Europe, so any time good
on the ends will be fine here.


On Tue, 22 Apr 2003, jw schultz wrote:

> On Tue, Apr 22, 2003 at 06:49:41PM +0100, John Bradford wrote:
> > > In light of our speaker sleeping through the meeting and
> > > the fact that kernel hackers tend not to be awake early
> > > in the morning I propose moving the time of the call to
> > > 1pm Pacific Time (GMT-0800). 
> > 
> > 10 PM U.K. time is no problem for me.
> 
> I think Hanna meant 1:00PM PDT (GMT-0700)  With UK on DST it
> is still 8 hours difference.  I think that also puts it
> around 6-8AM down under.

Please just give time in GMT and let us work it out! Between time zones
and daylight savings it's more confusing than useful.

Last week I went to Arizona from New York. It went like this: Sunday
morning 1hr forward for DST. Sunday later, 2hr back for central timezone. 
Sunday later 1hr more back, Arizona doesn't do DST, except... Monday, 1hr
forward again, the Navaho nation in AZ does do DST. At that point I set my
watch to GMT and told local time by the sun! Oh well, lots of brewpubs,
it's always time for a beer. 

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


  reply	other threads:[~2003-04-25 17:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 17:44 LSE conference call John Bradford
2003-04-18 19:58 ` Cliff White
2003-04-18 22:08   ` William Lee Irwin III
2003-04-19 10:03     ` John Bradford
2003-04-22 17:43     ` Hanna Linder
2003-04-22 17:49       ` John Bradford
2003-04-23  1:13         ` jw schultz
2003-04-25 17:55           ` Bill Davidsen [this message]
2003-04-25 18:26             ` John Bradford
2003-05-02 15:33               ` Scott Robert Ladd
2003-05-03 14:17                 ` Eric W. Biederman
2003-05-03 22:11                   ` H. Peter Anvin

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=Pine.LNX.3.96.1030425134717.16623B-100000@gatekeeper.tmr.com \
    --to=davidsen@tmr.com \
    --cc=hannal@us.ibm.com \
    --cc=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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).