From: "David du Colombier" <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9legacy venti-p9p, etc
Date: Sun, 27 Jun 2021 00:04:09 +0200 [thread overview]
Message-ID: <996d0057-bfbe-400a-bf6b-b73976d622e0@www.fastmail.com> (raw)
In-Reply-To: <20210626194728.tjchasvuwz4a5oml@sdf.org>
> venti-9p9, fossil-libventi, fossil-libventi-p9p, anyone with some
> experience with this? It's worthy?
I highly recommend the fossil-libventi patch. The purpose
of this change is to get rid of the old liboventi and use
the new libventi and libthread. liboventi can be removed
after this patch.
On the other side, the venti-p9p patch includes more experimental
changes, like the support of blocks larger than 56 KB. I wouldn't
recommend this patch.
--
David du Colombier
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tac4d36dfa36d502c-M4807cd892cb4521f8a3686b8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-06-26 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 19:47 adr via 9fans
2021-06-26 22:04 ` David du Colombier [this message]
2021-06-26 23:40 ` adr via 9fans
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=996d0057-bfbe-400a-bf6b-b73976d622e0@www.fastmail.com \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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).