From: Russ Cox <rsc@swtch.com>
To: plan9port-dev <plan9port-dev@googlegroups.com>
Subject: Re: [9fans] fossil in Plan 9 from User Space
Date: Tue, 20 Oct 2009 17:00:25 -0700 [thread overview]
Message-ID: <dd6fe68a0910201700x12f0e026jcc1d9ffc9f418826@mail.gmail.com> (raw)
In-Reply-To: <20091020165301757382.0498c09e@yahoo.co.uk>
-9fans, +plan9port-dev
On Tue, Oct 20, 2009 at 4:53 PM, Albert Skye <mistlail@yahoo.co.uk> wrote:
> I'm wondering if/when fossil might become part of plan9port. I found only a thread from 2007 mentioning that it had not been ported.
>
> It is of particular interest to me because I'm preparing various machines (which are not supported by Plan 9) to manage data on dedicated disks. My thought was to use Plan 9 from User Space, under BSD or Linux as necessary (defending upon hardware support), and fossil to provide a consistent interface to these dedicated disks, and to ensure portability (in case the disks were moved to new platform; to avoid migrating the data to a new file system).
>
>
prev parent reply other threads:[~2009-10-21 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 23:53 Albert Skye
2009-10-21 0:00 ` Russ Cox [this message]
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=dd6fe68a0910201700x12f0e026jcc1d9ffc9f418826@mail.gmail.com \
--to=rsc@swtch.com \
--cc=plan9port-dev@googlegroups.com \
/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).