comment and update todo

This commit is contained in:
Joey Hess 2023-06-23 12:25:08 -04:00
parent 0da5e9730d
commit 8d09207a2d
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 19 additions and 3 deletions

View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2023-06-23T16:07:39Z"
content="""
@mih it's still only a draft. See
[[todo/add_import_tree_to_external_special_remote_protocol]]
What I would like to do is work on implementing it in concert with someone
making a special remote that uses it, so we can find the pain points and
iterate a bit and hopefully improve it.
"""]]

View file

@ -1,9 +1,13 @@
The external special remote protocol supports export tree, but not yet
import tree. There is a draft protocol extension.
import tree. There is a draft protocol extension in
[[design/external_special_remote_protocol/export_and_import_appendix]].
My main concern about this is, will external special remotes pick good
ContentIdentifiers and will they manage the race conditions documented in
[[import_tree]]? Mistakes in these things can result in data loss, and it's
ContentIdentifiers and will they implement STOREEXPORTEXPECTED
in a way that avoids race conditions (at least as well as git does)?
See [the original import tree todo for discussion about the race conditions](http://source.git-annex.branchable.com/?p=source.git;a=blob;f=doc/todo/import_tree.mdwn;hb=a9db0a505592bf7ee1db24c45b19ebbc96066a55).
Mistakes in these things can result in data loss, and it's
rather subtle stuff. --[[Joey]]
> It may be better to implement [[importtree_only_remotes]] and make