working toward git-remote-annex using a special remote
Not quite there yet. Also, changed the format of GITBUNDLE keys to use only one '-' after the UUID. A sha256 does not contain that character, so can just split at the last one. Amusingly, the sha256 will probably not actually be verified. A git bundle contains its own checksums that git uses to verify it. And if someone wanted to replace the content of a GITBUNDLE object, they could just edit the manifest to use a new one whose sha256 does verify. Sponsored-by: Nicholas Golder-Manning
This commit is contained in:
parent
f4ba6e0c1e
commit
483887591d
3 changed files with 115 additions and 29 deletions
|
@ -3,11 +3,13 @@ This adds two new object types to git-annex, GITMANIFEST and a GITBUNDLE.
|
|||
GITMANIFEST--$UUID is the manifest for a git repository stored in the
|
||||
git-annex repository with that UUID.
|
||||
|
||||
GITBUNDLE--$UUID--sha256 is a git bundle.
|
||||
GITBUNDLE--$UUID-sha256 is a git bundle.
|
||||
|
||||
# format of the manifest file
|
||||
|
||||
An ordered list of bundle keys, one per line.
|
||||
An ordered list of bundle keys, one per line.
|
||||
|
||||
(Lines end with unix `"\n"`, not `"\r\n"`.)
|
||||
|
||||
# fetching
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue