aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-12-13 10:57:11 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-12-13 10:57:11 -0400
commit1d359620940f5b8c2476c5a32ee9922b5d53bb4f (patch)
tree83ddb1d65d8080599491657d9ca24fc769ffca40
parent4e899b306166533c7b2d6b6ac2dc44dd3453a107 (diff)
analysis
-rw-r--r--doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment
index 9541f1d74..4f82db153 100644
--- a/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment
+++ b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment
@@ -19,4 +19,6 @@ timestamp, and indeed the same timestamp is used for all the batch
changes. With the same timestamp for the log line that sets c as the line
that removes it, it's indeterminite which line will be acted on first, and
so the removal can be processed before the addition, leaving c "stuck".
+
+Fixing..
"""]]