From: Wladimir Mutel <mwg@fluffy.isd.dp.ua>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Identity
Date: Mon, 8 Jul 2002 10:47:59 +0000 [thread overview]
Message-ID: <slrnaiipjp.g7s.mwg@fluffy.isd.dp.ua> (raw)
In-Reply-To: <20020624224954.AE67C1999B@mail.cse.psu.edu>
> // my wife would like to know how Amidala managed to fit
> // quite so many changes of clothing into one small suitcase.
> the suitcase was a physical venti: similar portions of the
> various garments were only stored once. since storage and
> retrieval time of a suitcase is seldom much of an issue,
> the venti could be configured with a very small block
> size, resulting in substantial savings.
How small ? Not less than the length of SHA1 hash, or else savings
would not be substantial . :>
next prev parent reply other threads:[~2002-07-08 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 22:45 anothy
2002-07-08 10:47 ` Wladimir Mutel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 9:38 Fco.J.Ballesteros
2002-06-24 9:50 ` Nigel Roles
2002-06-24 19:16 ` Dan Cross
2002-06-24 9:35 Andrew Simmons
2002-06-22 13:47 rob pike, esq.
2002-06-22 19:09 ` Dan Cross
2002-06-24 9:45 ` balajis
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=slrnaiipjp.g7s.mwg@fluffy.isd.dp.ua \
--to=mwg@fluffy.isd.dp.ua \
--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).