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:29:46 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-06-20 22:29:46 -0400
commit53706ad9bf9bf22359154edab0ca61acea9027e1 (patch)
tree8207e327cbce18a4132571f390a92a6a463cfe9b /doc/bugs/git_annex_unlock_is_not_atomic.mdwn
parenta9a464914887b953d216fc2af8c691b0ee9b61d7 (diff)
move bug report
Diffstat (limited to 'doc/bugs/git_annex_unlock_is_not_atomic.mdwn')
-rw-r--r--doc/bugs/git_annex_unlock_is_not_atomic.mdwn5
1 files changed, 5 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
new file mode 100644
index 000000000..a7751f6b7
--- /dev/null
+++ b/doc/bugs/git_annex_unlock_is_not_atomic.mdwn
@@ -0,0 +1,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.