From 4d9f41694960a5708cffc0b1eec4b62dc1eb0825 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 4 Dec 2020 00:00:40 -0400 Subject: [PATCH] idea --- ..._fc336d8da2a449cb7c74cc2e48a43ba6._comment | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/todo/borg_special_remote/comment_7_fc336d8da2a449cb7c74cc2e48a43ba6._comment diff --git a/doc/todo/borg_special_remote/comment_7_fc336d8da2a449cb7c74cc2e48a43ba6._comment b/doc/todo/borg_special_remote/comment_7_fc336d8da2a449cb7c74cc2e48a43ba6._comment new file mode 100644 index 0000000000..7e24f83d81 --- /dev/null +++ b/doc/todo/borg_special_remote/comment_7_fc336d8da2a449cb7c74cc2e48a43ba6._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2020-12-04T01:17:01Z" + content=""" +The Remote interface recently got importKey, which gets us +unexpectedly a *lot* closer to making `git-annex import --from borg` a reality! + +The Remote would need a listImportableContents that finds all annex objects +in all (new) snapshots, and generates a ContentIdentifier that is just the +snapshot plus object path. Then importKey can simply generate a Key from +that ContentIdentifier without doing any more work. (And, so getting an +object from the remote will also work, because it will have the +ContentIdentifier recorded and so will know what snapshot and path in the +borg repo.) + +Seems that all that would be needed is a way to skip generating the git tree +for the imported files, since it would be useless. +And a way to force --no-content, since importing from a borg backup should not +get all the backed up annex objects. It may be best to make this a new +command, that just happens to use the ImportActions interface. +"""]]