{i} This page does not meet our wiki style guidelines. Please
help improve this page by cleaning up its formatting.  In
http://selenic.com/pipermail/mercurial/2008-June/019561.html,
mpm listed repository layout requirements (quote from that
post):  Here are the repo layout requirements:  ﻿a) does not
randomize disk layout (ie hashing) ﻿b) avoids case collisions c)
uses only ASCII ﻿d) handles stupidly long filenames e) avoids
filesystem quirks like reserved words and characters f) mostly
human-readable (optional) g) reversible (optional)  (a) is
important for performance. Filesystems are likely to store
sequentially created files in the same directory near each other
on disk. Disks and operating systems are likely to cache such
data. Thus, always reading and writing files in a consistent
order gives the operating system and hardware its best
opportunity to optimize layout. Ideally, the store layout should
roughly mirror the working dir layout.  ﻿Point (g) is
interesting. If we throw out cryptographically-stron