From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] rio too heavily optimized ;)
Date: Tue, 16 Apr 2019 17:53:32 +0200 [thread overview]
Message-ID: <CAFSF3XM1Dz+FL8cubq047+hKi8mPNS8g+w6E-gvTqxMCD0T_fg@mail.gmail.com> (raw)
In-Reply-To: <e0efb10f-a6d3-46ef-a469-f564be266a8f@www.fastmail.com>
you might also notice that rio is a lot more responsive over high
latency connections than it was before all these changes.
next prev parent reply other threads:[~2019-04-16 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 11:00 Ethan Gardener
2019-04-16 15:53 ` hiro [this message]
2019-04-16 15:59 ` [9front] " BurnZeZ
2019-04-20 11:38 ` Ethan Gardener
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=CAFSF3XM1Dz+FL8cubq047+hKi8mPNS8g+w6E-gvTqxMCD0T_fg@mail.gmail.com \
--to=23hiro@gmail.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).