diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawmL8pteP2jbYJUn1M3CbeLDvz2SWAA1wtg <Kristian@web> | 2011-06-20 21:03:00 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-06-20 21:03:00 +0000 |
| commit | dd4de9deb464adb6631585abd3c5a7e1401c8c6f (patch) | |
| tree | 9a680f9d34da538b6007f9c045c96b7043556463 | |
| parent | 601b07196ee122b96c984133637b4e2c3debc4b6 (diff) | |
| -rw-r--r-- | doc/forum/git_annex_unlock_is_not_atomic.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
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 000000000..a7751f6b7 --- /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. |