9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] admin with fossil?
Date: Fri, 10 Oct 2003 15:46:04 +0100	[thread overview]
Message-ID: <36fe3982fad9a0242c53d65752a361b4@caldo.demon.co.uk> (raw)
In-Reply-To: <20031010140614.GB2749@tfraser.cs.umd.edu>

>>the way of the future.  Which filesystem is more appropriate for my
>>stand-alone terminal, fossil or kfs?

fossil/venti should be fine.  i've certainly switched my thinkpad
from kfs to fossil without fuss.  it backs up to venti on the
same device, mainly so i can recover the fossil more easily if required.

functionally, fossil has got long names (sometimes useful) but
more important, snapshots and archives, which kfs hasn't.


      parent reply	other threads:[~2003-10-10 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 14:06 Tim Fraser
2003-10-10 14:20 ` David Presotto
2003-10-10 14:46 ` Charles Forsyth [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=36fe3982fad9a0242c53d65752a361b4@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.co.uk \
    --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).