From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] farewell to /sys/src/fs and IL
Date: Fri, 31 Aug 2007 15:15:23 -0400 [thread overview]
Message-ID: <441b0e457c0bcbb99f8e738c20da0e5e@coraid.com> (raw)
In-Reply-To: <8ccc8ba40708311204x7fe20b3cl565f7b8216cd1b75@mail.gmail.com>
i wrote a paper on how i ported history from ken's fs to ken's fs.
i think the technique would work for porting history from any fs
to any fs. /n/sources/contrib/quanstro/history.ms
however, we have a working kenfs. kenfs has been stable for a
very long time. venti+fossil has been problematic for us. i
would perfer not to switch.
- erik
next prev parent reply other threads:[~2007-08-31 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 22:27 geoff
2007-08-31 18:22 ` erik quanstrom
2007-08-31 18:42 ` Skip Tavakkolian
2007-08-31 19:03 ` Francisco J Ballesteros
2007-08-31 19:04 ` Francisco J Ballesteros
2007-08-31 19:15 ` erik quanstrom [this message]
2007-08-31 19:23 ` erik quanstrom
2007-08-31 22:12 ` Steve Simon
2007-08-31 19:14 ` Eric Van Hensbergen
2007-08-31 19:42 ` geoff
2007-08-31 19:30 ` geoff
2007-08-31 19:35 ` 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=441b0e457c0bcbb99f8e738c20da0e5e@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).