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

export appendonly support

Browse source 
Make `git annex export` check appendonly when removing a file from an
export, and not update the location log, since the remote still contains
the content.

This commit was supported by the NSF-funded DataLad project.
This commit is contained in:
Joey Hess 2018-08-30 11:18:20 -04:00
parent 02630b39ee
commit 8b39db20b5
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 15 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/todo/versioning_in_export_remotes.mdwn
View file

@ -31,7 +31,7 @@ won't be updated, as discussed above.
## final plan
Add an "appendOnly" field to Remote, indicating it retains all content stored
in it.
in it. done
Let S3 remotes be configured with versioned=yes or something like that
(what does S3 call the feature?) which enables appendOnly.
@ -43,7 +43,7 @@ Make S3 refuse to removeKey when configured appendOnly, failing with an error.
Make `git annex export` check appendOnly when removing a file from an
export, and not update the location log, since the remote still contains
the content.
the content. done
Make git-annex sync and the assistant skip trying to drop from appendOnly
remotes since it's just going to fail.
@ -52,8 +52,6 @@ Make exporttree=yes remotes that are appendOnly be trusted, and not force
verification of content, since the usual concerns about losing data when an
export is updated by someone else don't apply.
Make bup an appendOnly remote.
When a file was deleted from an exported tree, and then put back
in a later exported tree, it might get re-uploaded even though the content
is still retained in the versioned remote. S3 might have a way to avoid