diff options
Diffstat (limited to 'doc/specification')
| -rw-r--r-- | doc/specification/remote-protocol.org | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/specification/remote-protocol.org b/doc/specification/remote-protocol.org index 171934c8..dea7177e 100644 --- a/doc/specification/remote-protocol.org +++ b/doc/specification/remote-protocol.org @@ -44,7 +44,7 @@ where ~<entries>~ is a sequence (without newlines) of ~<entry>~, and each file (~100755~), a tree (~040000~), or a symbolic link (~120000~). More information on how git internally stores its objects can be found in the official [[https://git-scm.com/book/en/v2/git-Internals-git-Objects][git -documenation]]. +documentation]]. Since git hashes blob content differently from trees, this type of information has to be transmitted in addition to the content and the hash. To this aim, just @@ -133,7 +133,7 @@ corresponding git tree id to the client instead of a flat list of all recursively generated output directories as part of a ~Tree~ Protobuf message as it is done in the original protocol. The remote side promises that each blob and subtree contained in the root tree is available in the remote CAS. Such blobs -and trees must be accessible, using the streaming interface, without specifiying +and trees must be accessible, using the streaming interface, without specifying the size (since sizes are not stored in a git tree). Due to the Protobuf 3 specification, which is used in this remote execution API, not specifying the size means the default value 0 is used. |