From: "Andrew Simmons" <andrew.simmons@monitorbm.co.nz>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Qid path generation
Date: Tue, 6 May 2003 13:23:23 +1200 [thread overview]
Message-ID: <01c901c3136e$16616dc0$3f00a8c0@MERCURY> (raw)
In-Reply-To: <1b899d420ced031fb566de867397fc17@plan9.bell-labs.com>
> By the way, here's my hash function. I pass it the full path
> name and creation time:
>
Thanks, I'll give that a go. I don't know much about the theory of hash
keys. Does the addition of the creation date to the path significantly
reduce the likelihood of collisions?
next prev parent reply other threads:[~2003-05-06 1:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 21:29 Andrew Simmons
2003-05-05 21:30 ` W. Josephson
2003-05-05 21:33 ` rsc
2003-05-05 21:45 ` Andrew Simmons
2003-05-06 11:29 ` Aharon Robbins
2003-05-06 1:09 ` David Presotto
2003-05-06 1:10 ` David Presotto
2003-05-06 1:23 ` Andrew Simmons [this message]
2003-05-06 2:29 ` David Presotto
2003-05-06 3:05 ` Russ Cox
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='01c901c3136e$16616dc0$3f00a8c0@MERCURY' \
--to=andrew.simmons@monitorbm.co.nz \
--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).