From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] θfs vs webfs; θfs vs lookman
Date: Thu, 22 May 2014 13:08:58 -0700 [thread overview]
Message-ID: <CAJSxfmLtBXG8=F5NTgyUKh6Kw+iZ0itn1ykDxg+x_4qSXK2syQ@mail.gmail.com> (raw)
In-Reply-To: <82c33f112f41edda01a4074fd1a24a3b@ladd.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
cool!
what types of metadata are/were stored in a typical case?
On Thu, May 22, 2014 at 11:41 AM, erik quanstrom <quanstro@quanstro.net>wrote:
> i think i've fixed the issues preventing
> readweb http://www.9atom.org/magic/man2html/4/θfs
> and
> lookman θfs
> from working. it's surprising how many unicode bugs there still are.
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 875 bytes --]
next prev parent reply other threads:[~2014-05-22 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 18:41 erik quanstrom
2014-05-22 20:08 ` Skip Tavakkolian [this message]
2014-05-22 20:22 ` erik quanstrom
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='CAJSxfmLtBXG8=F5NTgyUKh6Kw+iZ0itn1ykDxg+x_4qSXK2syQ@mail.gmail.com' \
--to=skip.tavakkolian@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).