Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cmsc818fall2023projects
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Peter Keleher
cmsc818fall2023projects
Commits
55a98272
Commit
55a98272
authored
1 year ago
by
Peter J. Keleher
Browse files
Options
Downloads
Patches
Plain Diff
auto
parent
65439eae
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
p4.md
+3
-3
3 additions, 3 deletions
p4.md
with
3 additions
and
3 deletions
p4.md
+
3
−
3
View file @
55a98272
...
...
@@ -80,16 +80,16 @@ characters. The path to the root is "". A path from the
root to the a leaf in a depth 4 (height 3 in the usual nomenclature)
will be a string of length 3, e.g.: "Z4A".
The build RPC will return the
*blob tree hash*
(hash of top node in
The
*
build
*
RPC will return the
*blob tree hash*
(hash of top node in
the merkle tree). A server saves all blob trees it has built in
response to remote requests, never garbage-collecting. The build RPC should also return
the total number of blob hashes in the tree.
Since the
trees
are
persistent
,
a client can then navigate the remote tree
A remote build
trees
is
persistent
in the remote server's memory, so
a client can then navigate the remote tree
via the
*path*
RPC. Arguments are the blob tree hash and a path
string. The return value will include an array of
*sigs*
that describe
the children of the node defined by the blob tree hash and the
path. The children are blob hashes if the node is a leaf, or hashes
path. The children are blob hashes
(
*sigs*
)
if the node is a leaf, or hashes
of hashes otherwise.
*
The hash of a node is defined as the hash of the concatenation of the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment