comment

diff --git a/doc/todo/calckey___91__--path__93___given_a_checksum_and_filename__63__/comment_2_2cdaffbc72d5ef197a3ef7ffb306312e._comment b/doc/todo/calckey___91__--path__93___given_a_checksum_and_filename__63__/comment_2_2cdaffbc72d5ef197a3ef7ffb306312e._comment
new file mode 100644 (file)
index 0000000..2d0046c
--- /dev/null
+++ b/doc/todo/calckey___91__--path__93___given_a_checksum_and_filename__63__/comment_2_2cdaffbc72d5ef197a3ef7ffb306312e._comment
@@ -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.
+"""]]