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

comment

Browse source
This commit is contained in:
Joey Hess 2020-11-12 12:59:27 -04:00
parent b1eb47599a
commit c5141b469a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
doc/todo/calckey___91__--path__93___given_a_checksum_and_filename__63__/comment_2_2cdaffbc72d5ef197a3ef7ffb306312e._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2020-11-12T16:47:12Z"
content="""
Another approach would be to generate a SHA256 key, make the annex link,
and then use `git-annex migrate --backend=SHA256E` to convert the annex link.
And hmm, that does point toward a way to use the existing backend API
cleanly. Why bother with writing out the symlinks only to have migrate
convert them? The fastMigrate API has well-defined inputs, so we can just
expose it.
Eg:
git-annex examinekey SHA256--xxx --format="${key} ${objectpath}" \
--migrate-to-backend=SHA256E --filename=foo.tar.gz
--batch would need to input the filename as well as the key when
used with --migrate-to-backend.
"""]]