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

Merge branch 'master' into message-serialization

Browse source
This commit is contained in:
Joey Hess 2020-12-04 13:55:49 -04:00
commit 581792bcf0
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/todo/borg_special_remote/comment_7_fc336d8da2a449cb7c74cc2e48a43ba6._comment Normal file
View file

@ -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.
"""]]

1
doc/todo/serialize_Messages_for_transferkeys.mdwn
View file

@ -48,3 +48,4 @@ A few notes on implementing that:
new output type by sending the message through the pipe, and also
building any json object, and sending it through the pipe once it's done.
> Started work on this in the message-serialization branch. --[[Joey]]