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

comment

Browse source
This commit is contained in:
Joey Hess 2021-09-27 14:14:52 -04:00
parent 69c1c02339
commit a92427c0d3
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/todo/lockContent_for_special_remotes/comment_7_463e336fd7f2cb21eff2d87d25851c39._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2021-09-27T18:11:49Z"
content="""
It certainly must be possible to use a git-annex remote to handle locking
for special remotes, after all if you inverted control and had that
git-annex repository communicating to the user's reposities and telling
them when to delete from the special remote, that would be race safe.
But it seems that the usual git-annex remote operations are not sufficient
to do it. It would need some new operations tailored to support it.
"""]]