On Thu, Sep 27, 2012 at 11:36:19AM -0700, Shawn O. Pearce wrote: > > Interesting. I would have assumed it depended on order in the index. > > No. We tried that. Assigning bits by order in index (aka order of > SHA-1s sorted) results in horrible compression of the bitmap itself > because of the uniform distribution of SHA-1. Encoding instead by pack > order gets us really good bitmap compression, because object graph > traversal order tends to take reachability into account. So we see > long contiguous runs of 1s and get good compression. Sorting by SHA-1 > just makes the space into swiss cheese. Right, that makes a lot of sense. > > I think you are still OK, though, because > > the filename comes from the sha1 over the index file, which in turn > > includes the sha1 over the packfile. Thus any change in the packfile > > would give you a new pack and index name. > > No. The pack file name is composed from the SHA-1 of the sorted SHA-1s > in the pack. Any change in compression settings or delta windows or > even just random scheduling variations when repacking can cause > offsets to slide, even if the set of objects being repacked has not > differed. The resulting pack and index will have the same file names > (as its the same set of objects), but the offset information and > ordering is now different. Are you sure? The trailer is computed over the sha1 of the actual pack data (ordering, delta choices, and all), and is computed and written to the packfile via sha1close (see pack-objects.c, ll. 753-763). That trailer sha1 is fed into finish_tmp_packfile (l. 793). That function feeds it to write_idx_file, which starts a new sha1 computation that includes the sorted sha1 list and other index info. But before we sha1close that computation, we write the _original_ trailer sha1, adding it to the new sha1 calculation. See pack-write.c, ll. 178-180. And then that sha1 gets returned to finish_tmp_packfile, which uses it to name the resulting files. Am I reading the code wrong? -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html