From dd4de9deb464adb6631585abd3c5a7e1401c8c6f Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmL8pteP2jbYJUn1M3CbeLDvz2SWAA1wtg" Date: Mon, 20 Jun 2011 21:03:00 +0000 Subject: [PATCH] --- doc/forum/git_annex_unlock_is_not_atomic.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/git_annex_unlock_is_not_atomic.mdwn diff --git a/doc/forum/git_annex_unlock_is_not_atomic.mdwn b/doc/forum/git_annex_unlock_is_not_atomic.mdwn new file mode 100644 index 0000000000..a7751f6b7d --- /dev/null +++ b/doc/forum/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.