From c592c7e83613647db2256ac5351e63d09e2d7858 Mon Sep 17 00:00:00 2001 From: Alberto Sartori Date: Fri, 4 Nov 2022 12:11:30 +0100 Subject: fix a typo --- doc/specification/remote-protocol.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/specification') diff --git a/doc/specification/remote-protocol.org b/doc/specification/remote-protocol.org index f214f514..171934c8 100644 --- a/doc/specification/remote-protocol.org +++ b/doc/specification/remote-protocol.org @@ -103,7 +103,7 @@ object format. Using this git tree representation makes tree handling much more efficient, since the effort of traversing and uploading the content of a git tree occurs only once and for each subsequent request, we directly pass around the git tree -id. We require the invariant that if a tree is part of any CAS that all its +id. We require the invariant that if a tree is part of any CAS then all its content is also available in this CAS. To adhere to this invariant, the client side has to prove that the content of a tree is available in the CAS, before uploading this tree. One way to ensure that the tree content is known to the -- cgit v1.2.3