From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Patrick Mochel
<mochel-og82NyAXoxR0I81aPRRTmR2eb7JE58TQ@public.gmane.org>
Cc: Linux-pm mailing list <linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: IRC Meeting
Date: Tue, 15 Mar 2005 09:25:10 +1100 [thread overview]
Message-ID: <1110839111.5863.28.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.50.0503111306480.19793-100000-x8k/2hhmB0w5etPau2IXcQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 967 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?
>
> 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:
Can we post the agreed date/hours of the IRC meeting somewhere ? Or have
something re-post them at least 1 day before the meeting ? I'm bad at
managing my own time :)
Ben.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-03-14 22:25 UTC|newest]
Thread overview: 21+ 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
2005-03-14 22:25 ` Benjamin Herrenschmidt [this message]
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
2024-03-07 5:04 IRC meeting Arisu Tachibana
2024-04-18 6:04 Arisu Tachibana
2024-04-18 15:55 ` Jan Kiszka
2024-10-08 10:54 Arisu Tachibana
2024-10-31 8:21 Arisu Tachibana
2024-11-13 16:26 Arisu Tachibana
2024-12-05 2:36 Arisu Tachibana
2025-06-12 2:14 Arisu Tachibana
2025-06-17 3:59 Arisu Tachibana
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=1110839111.5863.28.camel@gaston \
--to=benh-xvmvhmargas8u2djnn8i7kb+6bgklq7r@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.