diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-07-12 14:19:26 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-07-12 14:19:26 -0400 |
| commit | 2596f24a996ec9d16ce125add1794c23af828b43 (patch) | |
| tree | f212e5b18eb19fa858c01524fc939283364592c3 | |
| parent | d67bdf48e3ef27aac66a38ffabbee007eed5b75a (diff) | |
comment
| -rw-r--r-- | doc/design/exporting_trees_to_special_remotes/comment_6_3217c2f852e5d9b1e4be2adff995dd24._comment | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_6_3217c2f852e5d9b1e4be2adff995dd24._comment b/doc/design/exporting_trees_to_special_remotes/comment_6_3217c2f852e5d9b1e4be2adff995dd24._comment new file mode 100644 index 000000000..4b1265bdd --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_6_3217c2f852e5d9b1e4be2adff995dd24._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2017-07-12T18:09:00Z" + content=""" +That would almost work without any smarts on the git-annex side. +When it tells the special remote to `REMOVEEXPORT`, the special remote +could remove the file from the HEAD equivilant but retain the content in its +versioned snapshots, and keep the url to that registered. But, that +doesn't actually work, because the url is registered for that special +remote, not the web special remote. Once git-annex thinks the file has been +removed from the special remote, it will never try to use the url +registered for that special remote. + +So, to support versioning-capable special remotes, there would need to be +an additional response to `REMOVEEXPORT` that says "I removed it from HEAD, +but I still have a copy in this url, which can be accessed using +the web special remote". +"""]] |