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

Added a comment: lockContent for special remotes w/o changing the protocol

Browse source
This commit is contained in:
Ilya_Shlyakhter 2021-04-12 01:20:16 +00:00 • committed by admin
parent a3d2e2a09e
commit cf60184992
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/todo/lockContent_for_special_remotes/comment_1_835d075d22fd1544fc27b912ad3326d8._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="lockContent for special remotes w/o changing the protocol"
date="2021-04-12T01:20:13Z"
content="""
Maybe, can implement lockContent with the existing protocol? To lock a key, use `TRANSFER STORE` to store a lockfile to the remote, with the lockfile's key derived from the key being locked, and the lockfile's content storing details like when was the lock set and by whom. Before any `REMOVE` request, git-annex would use `CHECKPRESENT` on the lockfile key, and not count the key as present if the lockfile key exists.
Or, simpler, just store one special key into the remote indicating \"prevent all removals by git-annex instances other than this one\" before doing a series of removals, and `REMOVE` the key when removals end.
"""]]