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

response

Browse source
This commit is contained in:
Joey Hess 2023-04-07 12:52:43 -04:00
parent 868eb44562
commit b4e5f2b8a4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/forum/Batch_process__44___git_rm__44___and_locking/comment_1_6cb866b48f6426e7ecc4f8d6af5b710d._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-04-07T16:42:16Z"
content="""
The lock you need to worry about here is for `.git/index`,
which both `git rm` and `git-annex addurl` need to modify
(when the latter is adding new files, not adding urls to existing files).
Unfortunately git's handling of that lock file doesn't play well with multiple
processes (unlike git-annex's other lock files that it uses).
With --batch, git-annex reads a line, handles it, outputs a response, and
waits for the next line. It should not keep any lock held while it's
waiting for the line. So, you should be able to schedule your `git rm`
to happen at that point and not have problems with locks colliding.
"""]]