From 8d09207a2d7f0ec0d1f021f93626ff2dca54052f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 23 Jun 2023 12:25:08 -0400 Subject: [PATCH] comment and update todo --- ...mment_2_6bea5a316df43a8306fb1cb19192db3f._comment | 12 ++++++++++++ ...ort_tree_to_external_special_remote_protocol.mdwn | 10 +++++++--- 2 files changed, 19 insertions(+), 3 deletions(-) create mode 100644 doc/design/external_special_remote_protocol/export_and_import_appendix/comment_2_6bea5a316df43a8306fb1cb19192db3f._comment diff --git a/doc/design/external_special_remote_protocol/export_and_import_appendix/comment_2_6bea5a316df43a8306fb1cb19192db3f._comment b/doc/design/external_special_remote_protocol/export_and_import_appendix/comment_2_6bea5a316df43a8306fb1cb19192db3f._comment new file mode 100644 index 0000000000..647c5a70fc --- /dev/null +++ b/doc/design/external_special_remote_protocol/export_and_import_appendix/comment_2_6bea5a316df43a8306fb1cb19192db3f._comment @@ -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. +"""]] diff --git a/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn b/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn index eda3fe5304..210e594b23 100644 --- a/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn +++ b/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn @@ -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