summaryrefslogtreecommitdiff
path: root/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-07-20 23:26:09 +0000
committerGravatar admin <admin@branchable.com>2013-07-20 23:26:09 +0000
commit9b2882573a3b3a750eac80e13d3156902c8cbe2c (patch)
tree0a4424ea94a22dc1f623b94e166ea0a859f09d26 /doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
parentdefeaf5bb9dc5878cf9fca10e7f3714aab301ae3 (diff)
Added a comment
Diffstat (limited to 'doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment')
-rw-r--r--doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
new file mode 100644
index 000000000..f7ae63cf8
--- /dev/null
+++ b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.154.0.140"
+ subject="comment 9"
+ date="2013-07-20T23:26:09Z"
+ content="""
+Ok, I've put in 2 separate bug fixes, any one of which would have been sufficient to prevent this data loss. Am working on a third fix to detect this kind of problem at a higher level and avoid losing content even if it gets all confused.
+
+This bug may be a candidate to be backported to Debian stable, since it causes data loss.
+"""]]