Stephan Beal wrote: >> #0 alone make the Z-card redundant. > > The Z-card is a separate check on the manifests contents, and isn't > actually its blob hash [snip] > The Z-card serves not to identify the checkin, but to validate that the > manifest itself has not changed since it was created.
I understand, but my point was the Z-card provides no assurances that the manifest's blob hash doesn't provide. If the former reveals that something's wrong, the latter will too. >> The NetBSD people would probably be happy to spend a few GB of disk space >> on that cache in exchange for Fossil being fast. As with Fossil's other >> caches and indexes, this would be built locally, not transferred over the >> network when syncing. > > So propose us a solution which doesn't break existing clients? How would generating and using a private cache on your own client break anybody else's client? _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
