From 953856df5fe3256626ea66401dc92db6bf26563c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 19 Nov 2018 13:28:44 -0400 Subject: [PATCH] comment --- ..._e13e593ba8c62ce630bc3456cb4e0f10._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/todo/add_prefix_option_to_export/comment_1_e13e593ba8c62ce630bc3456cb4e0f10._comment diff --git a/doc/todo/add_prefix_option_to_export/comment_1_e13e593ba8c62ce630bc3456cb4e0f10._comment b/doc/todo/add_prefix_option_to_export/comment_1_e13e593ba8c62ce630bc3456cb4e0f10._comment new file mode 100644 index 0000000000..07ef83bd33 --- /dev/null +++ b/doc/todo/add_prefix_option_to_export/comment_1_e13e593ba8c62ce630bc3456cb4e0f10._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-11-19T17:19:54Z" + content=""" +This would complicate the data structures git-annex needs for an export remote. + +Notably, git-annex relies on location tracking information in the git-annex +branch, which tracks whether or not a remote contains an object. With +multiple subdirectories in the same remote, one could contain an object and +another one not. There's no way to record that without some kind of unique +identifier for each tree in the remote. + +So I think this is better handled by initializing one remote per export +directory, and using something like S3's fileprefix= option. Of the remotes +supporting exporttree so far, only S3 has such a thing; it would make sense +to add it to webdav, and perhaps rsync and adb. (Seems that for directory +it's easier to just make a new directory.) + +Can I ask what type of special remote you were wanting this feature for? +"""]]