From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Cc: ori@eigenstate.org, red@redfrey.com
Subject: Re: [9fans] FOSDEM 2026 Plan 9 Devroom - Call for Participation
Date: Thu, 11 Dec 2025 22:52:37 +0000 [thread overview]
Message-ID: <CAOw7k5giTWF1Z_+U5pRP37NtnKvQK8vj_4W0tksP14XDTqtBDQ@mail.gmail.com> (raw)
In-Reply-To: <66F52E46FBBEF5826295C1ABBE12B46B@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
i've just booked some flights as well.
On Tue, 2 Dec 2025 at 14:22, <ori@eigenstate.org> wrote:
> Quoth red@redfrey.com:
> > > Ori Bernstein <ori@eigenstate.org>:
> > > I think there's a pretty good chance I'd be in if this happens.
> >
> > Thanks Ori, that's great to hear!
> >
> > I'm planning to setup a 9p share acting as the workspace for the
> > devroom and as an archive afterwards.
> >
> > Since FOSDEM's deadline is coming up, maybe we can start coordinating
> > a draft proposal.
> >
> > Would you be up for coordinating on it?
>
> And, I'm in; looks like I'll be talking a bit about GEFS. For IWP9
> attendees, most of it will be familiar, but there are a few updates
> since.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T77410da93c32c268-M55e703949c61f4a9fc76b6af
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2434 bytes --]
next prev parent reply other threads:[~2025-12-11 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 7:06 [9fans] FOSDEM 2026 Plan 9 Devroom - Call for Participation red
2025-10-06 14:14 ` qwx via 9fans
2025-10-07 3:38 ` red
2025-12-01 16:39 ` ori
2025-12-11 22:52 ` Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-06 7:04 red
2025-09-30 6:39 red
2025-10-06 0:29 ` Ori Bernstein
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=CAOw7k5giTWF1Z_+U5pRP37NtnKvQK8vj_4W0tksP14XDTqtBDQ@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
--cc=ori@eigenstate.org \
--cc=red@redfrey.com \
/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).