diff options
author | 2016-05-04 13:16:22 -0400 | |
---|---|---|
committer | 2016-05-04 13:16:22 -0400 | |
commit | dac5c89a083fac8ab5a521af1cad7d4c04aca105 (patch) | |
tree | 422479325b922e0795ab9c01f5c2cc0aca2dc7c2 | |
parent | 9c4227ad51fd04ef70e224a328e7d36403d53458 (diff) |
response
-rw-r--r-- | doc/forum/race_condition_with_drop_-J__63__/comment_1_0607c11410d99a6933e02c28b54c1f65._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/race_condition_with_drop_-J__63__/comment_1_0607c11410d99a6933e02c28b54c1f65._comment b/doc/forum/race_condition_with_drop_-J__63__/comment_1_0607c11410d99a6933e02c28b54c1f65._comment new file mode 100644 index 000000000..e6d235714 --- /dev/null +++ b/doc/forum/race_condition_with_drop_-J__63__/comment_1_0607c11410d99a6933e02c28b54c1f65._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-05-04T17:13:55Z" + content=""" +This can happen if the working tree contains two files that both point to +the same content. Since git-annex is dropping multiple files in parallel, +it might try to drop both files at the same time. One of the drops will +succeed, and the other fail as shown. + +It should be nothing to worry about since the content does get dropped. +"""]] |