summaryrefslogtreecommitdiff
path: root/doc/bugs/git_annex_unlock_is_not_atomic.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-06-20 22:38:18 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-06-20 22:38:18 -0400
commit9f9e17aa0f4898063a58c88661bca01465b126a9 (patch)
tree93145a4538c8e35a2223ed106a2475dc7faf4e2a /doc/bugs/git_annex_unlock_is_not_atomic.mdwn
parent53706ad9bf9bf22359154edab0ca61acea9027e1 (diff)
unlock: Made atomic.
Diffstat (limited to 'doc/bugs/git_annex_unlock_is_not_atomic.mdwn')
-rw-r--r--doc/bugs/git_annex_unlock_is_not_atomic.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_unlock_is_not_atomic.mdwn b/doc/bugs/git_annex_unlock_is_not_atomic.mdwn
index a7751f6b7..6d324ff50 100644
--- a/doc/bugs/git_annex_unlock_is_not_atomic.mdwn
+++ b/doc/bugs/git_annex_unlock_is_not_atomic.mdwn
@@ -3,3 +3,5 @@ Running a command like
git annex unlock myfile
is not atomic, that is if the execution is aborted you may end up with an incomplete version of myfile in the directory. If you don't notice this you may lock it again and then propagate this bad version of the file to your other repositories. A simple workaround is to simply name it something else while unlocking and then rename it to the correct filename once it's completely copied. I don't know Haskel yet so I can not fix this issue otherwise I would sure try. A part from this, I love git annex.
+
+> [[fixed|done]] --[[Joey]]