From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] hackathon writeup
Date: Thu, 18 Aug 2022 19:09:43 -0400 [thread overview]
Message-ID: <487BFCCD-9DF3-4C93-B648-DB77B3D36710@stanleylieber.com> (raw)
In-Reply-To: <CABB-WO9qWpXMK29P4zqXKRtGiR-+aB7z7qaar7Rm0Hg8v17n2g@mail.gmail.com>
please elaborate. this is your chance.
sl
> On Aug 18, 2022, at 6:53 PM, Stuart Morrow <morrow.stuart@gmail.com> wrote:
>
>
>>
>> As expected, there was pontificating about the next version of 9p,
>> and how to make it handle latency better. Ideas were floated and
>> rejected, and the difficulties were explored. While no solid
>> conclusions were reached, there are a few things we know are
>> essential to the making the next version better.
>
> Every time I see this discussed, I never see 9P.ix (code is in branch
> NxM of harvey-os) mentioned (either as something to adopt or with
> a reason why not to adopt). Just saying...
>
next prev parent reply other threads:[~2022-08-18 23:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 3:27 ori
2022-08-18 22:37 ` Stuart Morrow
2022-08-18 22:52 ` Stuart Morrow
2022-08-18 23:09 ` Stanley Lieber [this message]
2022-08-18 23:32 ` Stuart Morrow
2022-08-18 23:11 ` Kurt H Maier
2022-08-18 23:33 ` Stuart Morrow
2022-08-18 23:55 ` Jacob Moody
2022-08-19 0:05 ` ori
2022-10-14 5:45 ` 9p2000.ix (Was Re: [9front] hackathon writeup) unobe
2022-08-19 11:34 ` [9front] hackathon writeup Stuart Morrow
2022-08-19 13:21 ` Jacob Moody
2022-08-18 23:04 ` Stuart Morrow
2022-08-18 23:24 ` ori
2022-08-18 23:37 ` Stuart Morrow
2022-08-18 23:43 ` ori
2022-08-19 0:02 ` Kurt H Maier
2022-08-19 0:23 ` qwx
2022-08-19 1:54 ` Kurt H Maier
2022-08-19 2:02 ` qwx
2022-08-19 7:08 ` Steve Simon
2022-08-20 1:38 ` Xiao-Yong Jin
2022-08-20 3:57 ` ori
2022-08-19 19:52 ` Thaddeus Woskowiak
2022-08-19 21:13 ` David Arnold
2022-08-19 19:11 ` Aram Hăvărneanu
2022-08-19 20:40 ` Stuart Morrow
2022-08-20 13:14 ` Stuart Morrow
2022-08-22 17:54 ` Aram Hăvărneanu
2022-08-22 17:56 ` Kurt H Maier
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=487BFCCD-9DF3-4C93-B648-DB77B3D36710@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).