bfiles filename encoding

[Tom Conerly]

On windows bfiles is going to run into issues with the path length limit.
The pending or committed bfiles have ~60 characters added to their path (40
for the SHA and ~20 for .hg/bfiles/pending) which can easily push valid
paths over the limit. As far as I can tell we don't need the path for these
files we only need the SHA (so store them in
.hg/bfiles/[pending|committed]/SHA). There is no need to go from the hash
back to the path so using a hash we can't reverse is fine. This change would
also require all bfile stores to save files just using the SHA and not the
path which again is not a problem. Does this sound like a reasonable fix?

There is a similar issue with .hgbfiles but the files stored there are only
a 10 characters longer so it doesn't seem like its worthwhile to fix. To
decrease the risk further we could rename .hgbfiles to .hgb or some other
shorter name.

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100630/5b4a7a44/attachment.htm>