From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] FS to skip/put-together duplicate files
Date: Wed, 15 Aug 2007 09:42:27 +0900 [thread overview]
Message-ID: <8c67353e811dae824f940a60ad46e7a0@orthanc.cc.titech.ac.jp> (raw)
> does anyone have an example of a case where compression and uniquing are required?
I'm not sure about compression, but uniquing must be a very neat feature
when you want to build a P2P overlaid venti.
--
"on travel, off the network ... and a fossil in my pocket"
next reply other threads:[~2007-08-15 0:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 0:42 YAMANASHI Takeshi [this message]
2007-08-15 0:47 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 0:49 YAMANASHI Takeshi
2007-08-10 11:39 Enrico Weigelt
2007-08-10 11:51 ` Gabriel Diaz
2007-08-10 12:26 ` erik quanstrom
2007-08-13 3:32 ` YAMANASHI Takeshi
2007-08-13 12:01 ` erik quanstrom
2007-08-13 13:43 ` Francisco J Ballesteros
2007-08-13 13:52 ` erik quanstrom
2007-08-13 14:40 ` Francisco J Ballesteros
2007-08-14 13:16 ` erik quanstrom
2007-08-14 13:57 ` Steve Simon
2007-08-14 14:13 ` erik quanstrom
2007-08-14 15:02 ` David Leimbach
2007-08-14 16:18 ` Uriel
2007-08-14 16:25 ` erik quanstrom
2007-08-15 0:27 ` Uriel
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=8c67353e811dae824f940a60ad46e7a0@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.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).