From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] mounting fossil
Date: Thu, 14 Mar 2013 11:54:38 -0400 [thread overview]
Message-ID: <57b11f1cedc9ccfda2d6042575226a59@9srv.net> (raw)
In-Reply-To: <CAM6ozu5U6Jf1PLsoyZdu1Suz0UT-BUB0ZJbcFEGFjd6RWW4d-A@mail.gmail.com>
> I reorganize my data very often, moving between dirs, renaming,
> reorganising tree structure...
> How will Venti cope with this?
Well. Venti does block-level deduplication. If you have 100 MB of data
in dir A and move it to dir B, you're not going to duplicate that storage
(you'll get new blocks for the directory, of course, but that's both
minimal and unavoidable).
Anthony
next prev parent reply other threads:[~2013-03-14 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 8:35 Peter A. Cejchan
2013-03-14 9:41 ` David du Colombier
2013-03-14 14:23 ` a
2013-03-14 15:33 ` Peter A. Cejchan
2013-03-14 15:54 ` a [this message]
2013-03-15 7:43 ` Peter A. Cejchan
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=57b11f1cedc9ccfda2d6042575226a59@9srv.net \
--to=a@9srv.net \
--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).