From d8af254515b5135e5a2b2aacb20d995bfce38509 Mon Sep 17 00:00:00 2001 From: "vrs+annex@ea5fa24dbb279be61a8e50adb638bf8366300717" Date: Thu, 5 Apr 2018 01:32:33 +0000 Subject: [PATCH] Added a comment --- ...comment_2_0966f8bf944ded0a5199285ed3c12930._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/annex.genmetadata_should_default_to_true/comment_2_0966f8bf944ded0a5199285ed3c12930._comment diff --git a/doc/bugs/annex.genmetadata_should_default_to_true/comment_2_0966f8bf944ded0a5199285ed3c12930._comment b/doc/bugs/annex.genmetadata_should_default_to_true/comment_2_0966f8bf944ded0a5199285ed3c12930._comment new file mode 100644 index 0000000000..cea41ad1db --- /dev/null +++ b/doc/bugs/annex.genmetadata_should_default_to_true/comment_2_0966f8bf944ded0a5199285ed3c12930._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="vrs+annex@ea5fa24dbb279be61a8e50adb638bf8366300717" + nickname="vrs+annex" + avatar="http://cdn.libravatar.org/avatar/74219abcec6eece8e2c9d4351c2c912c" + subject="comment 2" + date="2018-04-05T01:32:32Z" + content=""" +1. Not losing data (or alternatively having a great big warning in the manual, or requiring it as a configuration step) should be the default in software that manages files, especially software that advertises a backup usecase on its front page. I do think the current implementation could be improved, which is what I opened for. If that's not enough, a simple binary format should do the trick at about the same overhead as regular filesystems while staying future-proof. +2. Implementing timestamps with a field name that doesn't clash with existing fields should avoid this issue. +"""]]