From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9p vs http
Date: Tue, 16 Nov 2010 15:56:22 +0000 [thread overview]
Message-ID: <c3acdc252e425bc144d2c9e68badaef8@terzarima.net> (raw)
In-Reply-To: <AANLkTinZxeFVW0WduLM9Yod3u=p92PrR3kX=aWD5fMRA@mail.gmail.com>
>i'd say it's a bug. fossil could easily reserve some number of bits
>of the qid (say 20 bits) to make the files in the dump unique
>while still allowing space for a sufficient number of live files.
that's possibly closest to the intent of the qid discussion in intro(5), although
it's not clear that considers the possibility of aliases within a hiearchy,
where it might make more sense to have the Qid.path associated with the file,
regardless of how you got to it. even so, for dump it's not been a big problem
in practice only because one usually binds from the dump, not into it.
i'm sure that somewhere it was suggested that high order bits of Qid.path
should be avoided by file servers to allow for their use to make qids unique
but i haven't been able to find that.
next prev parent reply other threads:[~2010-11-16 15:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 3:25 Sam Watkins
2010-11-15 4:20 ` John Floren
2010-11-15 4:26 ` Bruce Ellis
2010-11-15 5:16 ` Sam Watkins
2010-11-15 5:26 ` John Floren
2010-11-15 14:09 ` Gorka Guardiola
2010-11-15 14:15 ` Gorka Guardiola
2010-11-15 15:37 ` roger peppe
2010-11-15 16:45 ` C H Forsyth
2010-11-15 16:37 ` roger peppe
2010-11-15 16:48 ` erik quanstrom
2010-11-15 17:02 ` roger peppe
2010-11-15 19:29 ` erik quanstrom
2010-11-15 21:38 ` roger peppe
2010-11-16 1:18 ` erik quanstrom
2010-11-16 12:12 ` roger peppe
2010-11-16 15:56 ` Charles Forsyth [this message]
2010-11-16 16:04 ` erik quanstrom
2010-11-16 16:32 ` Charles Forsyth
2010-11-16 17:11 ` roger peppe
2010-11-15 15:44 ` David Leimbach
2010-11-15 15:55 ` Venkatesh Srinivas
2010-11-15 15:57 ` David Leimbach
2010-11-15 18:44 ` Russ Cox
2010-11-15 19:00 ` Dan Adkins
2010-11-15 22:18 ` Yaroslav
2010-11-15 22:34 ` erik quanstrom
2010-11-16 12:42 ` 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=c3acdc252e425bc144d2c9e68badaef8@terzarima.net \
--to=forsyth@terzarima.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).