|
|
|
|
|
|
by pslam
2592 days ago
|
|
|
An easy example with git would be to create a pair of read-only repositories: one public-facing which is cloned by the general public, and one with (potentially entirely) different contents which can be selectively pulled depending on the client. There's a complication with the few appended trailing blocks being invalid data, but the format might allow it, and git doesn't verify its integrity recursively. |
|
|
Yes it does. On clone the entire history is recursively hashed, and incrementally on fetch.
There isn't even any place in the protocol to transfer pre-hashed content, it must be hashed to make it addressable.