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

remove last trailing unresolved bit

Browse source 
I think the lock file probing stuff is ok as it is for pid locks.
If not, let's wait until we have a test case, it would be easy to subtly
break it.
This commit is contained in:
Joey Hess 2021-12-06 15:34:56 -04:00
parent a91c4d945e
commit d4665731d9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 0 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/annex_get_should_retry_failed_downloads_from_S3/comment_10_1cbef11391d23210230872a75f8e5414._comment
View file

@ -5,12 +5,4 @@
content=""" content="""
Update: All problems noted above are fixed, fine-grained locking is merged, Update: All problems noted above are fixed, fine-grained locking is merged,
and it seems to work well! and it seems to work well!
Except for this, which I have not gotten to. It may not actually matter, but
worth looking at to be sure:
`getLockStatus` and `checkSaneLock` look at the status of the pid lock,
but not yet at the fine-grained STM lock status. And as implemented,
I think they never worked at all, since they check for posix locks on the
pid lock file.
"""]] """]]