mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2019-04-24 18:37:22 -04:00
commit fcf6a8851e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/internals/key_format.mdwn
View file

@ -26,5 +26,5 @@ a key. Older versions of git-annex would parse keys with the fields in other
orders (although the name field must always come last), but the current
version requires the fields come in the order shown above.
The `git annex examinekey` command can be used to extract information from
The [[`git annex examinekey`|git-annex-examinekey]] command can be used to extract information from
a key.

1
doc/todo/key_checksum_from_chunk_checksums.mdwn Normal file
View file

@ -0,0 +1 @@
Would it be hard to add a variantion to checksumming [[backends]], that would change how the checksum is computed: instead of computing it on the whole file, it would first be computed on file chunks of given size, and then the final checksum computed on the concatenation of the chunk checksums? You'd add a new [[key field|internals/key_format]], say cNNNNN, specifying the chunking size (the last chunk might be shorter). Then (1) for large files, checksum computation could be parallelized (there could be a config option specifying the default chunk size for newly added files); (2) I often have large files on a remote, for which I have md5 for each chunk, but not for the full file; this would enable me to register the location of these fies with git-annex without downloading them, while still using a checksum-based key.