From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] authoritative source for u9fs?
Date: Sun, 24 Jan 2021 23:30:01 +0000 [thread overview]
Message-ID: <CAOw7k5gqaY5R5nS0d0Z9X_Y7t0h3T1acu8ZLy5-aPVtSoa0Thg@mail.gmail.com> (raw)
In-Reply-To: <20210122.021534.1096985739466181664.dworkin@weaselfish.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
I've just accepted an important pull request to it that I missed, until I
looked at it in response to this, so you should do another pull to get that.
Generally, though it has been reasonably stable for some time. Changes are
often just to cope with this year's #ifdefs or feature defines.
On Fri, Jan 22, 2021 at 9:17 AM Dworkin Muller <dlm-9fans@weaselfish.com>
wrote:
> On Fri, 22 Jan 2021 03:20:03 -0500, Fazlul Shahriar <fshahriar@gmail.com>
> wrote:
> fshahriar> https://bitbucket.org/plan9-from-bell-labs/u9fs/src/master/
>
> That looks much more believable than the others. Thank you very much
> for the pointer.
>
> Dworkin
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tee2220301f2a891c-M74684f2bf32f35f0b7c76a2d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2308 bytes --]
next prev parent reply other threads:[~2021-01-24 23:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:01 Dworkin Muller
2021-01-22 8:20 ` Fazlul Shahriar
2021-01-22 9:15 ` Dworkin Muller
2021-01-22 9:36 ` Steve Simon
2021-01-24 23:30 ` Charles Forsyth [this message]
2021-01-24 23:34 ` Charles Forsyth
2021-01-25 0:10 ` Lyndon Nerenberg
2021-01-25 0:14 ` Charles Forsyth
2021-01-25 6:33 ` ori
2021-01-25 5:10 ` Lucio De Re
2021-01-25 5:52 ` Dworkin Muller
2021-01-27 16:23 ` Ethan Gardener
2021-01-27 18:49 ` Lucio De Re
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=CAOw7k5gqaY5R5nS0d0Z9X_Y7t0h3T1acu8ZLy5-aPVtSoa0Thg@mail.gmail.com \
--to=charles.forsyth@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).