diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2014-08-15 17:39:14 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-08-15 17:39:14 +0000 |
| commit | 0e9ea60d710bc49a5366fdd30174548bd77e0046 (patch) | |
| tree | a8cea42ccea410d3dd7c20ffa3b0ca5612beaa37 | |
| parent | b38491100168141f2a1daa089a5416a92014ec25 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/direct_command_leaves_repository_inconsistent_if_interrupted/comment_2_2f3fb399f976d96aa66310f11365207c._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/direct_command_leaves_repository_inconsistent_if_interrupted/comment_2_2f3fb399f976d96aa66310f11365207c._comment b/doc/bugs/direct_command_leaves_repository_inconsistent_if_interrupted/comment_2_2f3fb399f976d96aa66310f11365207c._comment new file mode 100644 index 000000000..b55e3c2a3 --- /dev/null +++ b/doc/bugs/direct_command_leaves_repository_inconsistent_if_interrupted/comment_2_2f3fb399f976d96aa66310f11365207c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.7" + subject="comment 2" + date="2014-08-15T17:39:14Z" + content=""" +I still cannot see a way that more than one file's content could end up in misctemp, since `git annex direct` moves just one file there at a time, so max of one should be there if interrupted. However, there was really no reason to be moving files through misctemp at all, so `git annex direct` now moves them into place completely atomically. + +Bug report retitled appropriatly for the `git annex lock --force` suprise. +"""]] |