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

update

Browse source
This commit is contained in:
Joey Hess 2021-04-12 14:13:44 -04:00
parent 1e322c329e
commit 67d91c63f7
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/todo/lockContent_for_special_remotes.mdwn
View file

@ -54,6 +54,12 @@ remotes, without needing to set mincopies to 0 and risk losing content.
there's nowhere in a directory special remote to record information about
locking problems with it. Getting this right seems hard..
> If lockContent throws an exception, that remote is treated the same
> as if it did not support lockContent, so if these problems can be
> differentiated from a failure to lock at all, can just throw an
> exception. But need to avoid lockContent succeeding in any case
> where removeKey will not be prevented from removing the content.
* S3 has an object lock feature, I don't know if it would be usable for
this.