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

comment

Browse source
This commit is contained in:
Joey Hess 2018-11-19 13:28:44 -04:00
parent e612633999
commit 953856df5f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
doc/todo/add_prefix_option_to_export/comment_1_e13e593ba8c62ce630bc3456cb4e0f10._comment Normal file
View file

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