comment
This commit is contained in:
parent
2d9b3e4510
commit
41b9d77201
1 changed files with 20 additions and 0 deletions
|
@ -0,0 +1,20 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 1"""
|
||||||
|
date="2018-12-09T15:05:20Z"
|
||||||
|
content="""
|
||||||
|
This is the same as concurrent `git add` (with or without git-annex)
|
||||||
|
failing due to git only allowing one writer to the index at a time.
|
||||||
|
|
||||||
|
Since this is a fundamental limitation of git, I feel that git-annex should
|
||||||
|
not try to work around it for things involving the worktree's index file,
|
||||||
|
except for within the same command as it does for `git annex add -J`.
|
||||||
|
|
||||||
|
`git annex fromkey` obviously does need to update the worktree's index
|
||||||
|
file. I suggest you run it in --batch mode and serialize the changes to it
|
||||||
|
that way.
|
||||||
|
|
||||||
|
(git-annex does of course work around the problem for the git-annex branch's index
|
||||||
|
file, but that's very different than the worktree index; it doesn't matter if
|
||||||
|
one process stages and commits another process's git-annex branch changes).
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue