9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Chris Collins <xfire-9fans@xware.cx>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan 9 developement irc meeting May 19 13:30 UTC
Date: Fri, 20 May 2005 02:27:50 +1000	[thread overview]
Message-ID: <20050519162750.GA15564@xware.cx> (raw)
In-Reply-To: <20050518053245.GB22576@server4.lensbuddy.com>

Uriel was once rumoured to have said:
> The first Plan 9 development irc meeting will be held May 19 13:30 UTC
> (09:30 EDT) in the usual #plan9 at irc.freenode.org (see Wiki IRC page for
> details).
> 
> Let me know if you can't attend and there is something that you think
> should be discussed. Logs will be published afterwards on the Wiki.

My notes of who is working on what has been published at:

http://nekohako.xware.cx/plan9devmeet/Notes-20050519.txt

C.


      parent reply	other threads:[~2005-05-19 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  5:32 Uriel
2005-05-19 14:46 ` Ronald G. Minnich
2005-05-19 15:06   ` Eric Van Hensbergen
2005-05-19 16:27 ` Chris Collins [this message]

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=20050519162750.GA15564@xware.cx \
    --to=xfire-9fans@xware.cx \
    --cc=9fans@cse.psu.edu \
    /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).