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

thoughts

Browse source
This commit is contained in:
Joey Hess 2022-05-10 14:17:29 -04:00
parent c5b5fd364a
commit b6c7819803
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/todo/command_to___34__migrate__34___from_adjusted_mode/comment_5_55b5beaeba0de7bb1efcc2626570d3b5._comment
View file

@ -31,8 +31,8 @@ fsck could lock the object file for drop, and then rather than removeing it,
move it to a holding location. Then it could move the object file move it to a holding location. Then it could move the object file
into the right place the same as `get` does. This should avoid the race. into the right place the same as `get` does. This should avoid the race.
Interrupting fsck at the wrong time would leave the object file in this Interrupting fsck at the wrong time would leave the object file in this
holding location though. If it used `.git/annex/tmp`, normal commands holding location though. Re-running fsck would need to recover from this
like `git-annex get` would recover from an interrupted fsck, though situation. Putting it in `.git/annex/tmp/` might make sense, although
they would need to do some work to rehash the tmp file. Re-running `git-annex get` does not necessarily recover when the object file is
fsck would need to also recover from an interrupted fsck. located there.
"""]] """]]