From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fossil; is the time right?
Date: Fri, 14 Mar 2003 08:16:38 -0800 [thread overview]
Message-ID: <1a1744b7a6c98ebc0dad5570fb1299f0@mightycheese.com> (raw)
In-Reply-To: <200303140959.h2E9xJt09672@augusta.math.psu.edu>
Go with fossil. I installed one on January second and it hasn't
let me down yet. You'll use less disk space and the snapshots
are nice, too. You're probably not talking about optical disk
for the backup, but I'm used to that and the speed of the dump
makes a difference.
-rob
next prev parent reply other threads:[~2003-03-14 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 9:59 Dan Cross
2003-03-14 12:21 ` Fco.J.Ballesteros
2003-03-14 16:16 ` rob pike, esq. [this message]
2003-03-14 13:39 rog
2003-03-14 14:57 ` Fco.J.Ballesteros
2003-03-14 19:00 ` Russ Cox
2003-03-14 23:54 ` Geoff Collyer
2003-03-14 15:10 rog
2003-03-14 15:13 ` Fco.J.Ballesteros
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=1a1744b7a6c98ebc0dad5570fb1299f0@mightycheese.com \
--to=rob@mightycheese.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).