From: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: Patrick Mochel
<mochel-og82NyAXoxR0I81aPRRTmR2eb7JE58TQ@public.gmane.org>
Cc: linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: IRC Meeting
Date: Fri, 11 Mar 2005 18:45:39 -0500 [thread overview]
Message-ID: <1110584740.12485.217.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.50.0503111306480.19793-100000-x8k/2hhmB0w5etPau2IXcQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Fri, 2005-03-11 at 13:26 -0800, Patrick Mochel wrote:
> Hi everyone.
>
> I think we should start having some IRC meetings next week. We have a lot
> to talk about, and a lot of ideas to kick around. I don't think we can, or
> should try, to talk about everything in one shot, so it would help to
> priortize and organize the meetings. :)
>
> That said, I think it would be good to have a few meetings in a row so we
> can get everything out on the table. Say, 1 per week for the first three
> weeks, then every other week. Would people be interested in that?
Yeah, I think it could be very useful.
>
> Thursday would work best for me next week, and seems like a good day
> anyway. For times, I suggest we rotate the time over the course of three
> weeks so we all get a good time and a painful one. :)
>
> How about this:
The latter two would work for me (US EST).
Thanks,
Adam
>
>
> Meeting 1:
>
> AU US PST US EST EU Time
> --
> 3/18, 00:00 3/17, 07:00 3/17, 10:00 3/17, 17:00
>
>
> Meeting 2:
>
> AU US PST US EST EU Time
> --
> 3/25, 07:00 3/24, 14:00 3/24, 17:00 3/24, 23:00
>
>
> Meeting 3:
>
> AU US PST US EST EU Time
> --
> 3/31, 15:00 3/30, 22:00 3/31, 01:00 3/31, 07:00
>
[-- Attachment #2: Type: text/plain, Size: 171 bytes --]
_______________________________________________
linux-pm mailing list
linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
http://lists.osdl.org/mailman/listinfo/linux-pm
next prev parent reply other threads:[~2005-03-11 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 21:26 IRC Meeting Patrick Mochel
[not found] ` <Pine.LNX.4.50.0503111306480.19793-100000-x8k/2hhmB0w5etPau2IXcQ@public.gmane.org>
2005-03-11 21:32 ` Nigel Cunningham
[not found] ` <1110576748.32510.18.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-03-11 21:41 ` Patrick Mochel
[not found] ` <Pine.LNX.4.50.0503111331390.19793-100000-x8k/2hhmB0w5etPau2IXcQ@public.gmane.org>
2005-03-11 21:53 ` Jordan Crouse
[not found] ` <20050311145331.42d16f50-aftB2sG12IhaqnLngUycEA@public.gmane.org>
2005-03-12 5:45 ` Nigel Cunningham
2005-03-11 23:45 ` Adam Belay [this message]
2005-03-14 22:25 ` Benjamin Herrenschmidt
2005-03-14 22:43 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 21:31 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3002F68137-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-03-11 21:42 ` Patrick Mochel
[not found] ` <Pine.LNX.4.50.0503111341560.19793-100000-x8k/2hhmB0w5etPau2IXcQ@public.gmane.org>
2005-03-12 0:32 ` Benjamin Herrenschmidt
2005-03-12 5:41 ` Pavel Machek
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=1110584740.12485.217.camel@localhost.localdomain \
--to=abelay-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=mochel-og82NyAXoxR0I81aPRRTmR2eb7JE58TQ@public.gmane.org \
/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