close wontfix

diff --git a/doc/bugs/annex.genmetadata_should_default_to_true.mdwn b/doc/bugs/annex.genmetadata_should_default_to_true.mdwn
index afc004ed0a65d00a76fbdd2533827bbedb2f98b8..5aef50d45b49028a8f704c83d114a4d8f85915b4 100644 (file)
--- a/doc/bugs/annex.genmetadata_should_default_to_true.mdwn
+++ b/doc/bugs/annex.genmetadata_should_default_to_true.mdwn
@@ -9,3 +9,5 @@ Add a file to a fresh annex, observe it has no metadata.
 
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 Yes I love it! (Except for its spotty timestamp support)
+
+> [[notabug|done]] --[[Joey]]

diff --git a/doc/bugs/annex.genmetadata_should_default_to_true/comment_5_8cd47851ca76005e0011da7c2f62d77d._comment b/doc/bugs/annex.genmetadata_should_default_to_true/comment_5_8cd47851ca76005e0011da7c2f62d77d._comment
new file mode 100644 (file)
index 0000000..69f6444
--- /dev/null
+++ b/doc/bugs/annex.genmetadata_should_default_to_true/comment_5_8cd47851ca76005e0011da7c2f62d77d._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2020-02-17T16:47:33Z"
+ content="""
+I agree with Ilya's points.
+
+And it's unresonable to characterize this as data loss, because git itself
+does not store file timestamp data. Making such mischaracterizations does,
+however, cause me, as the maintainer, to wonder if this is a feature that
+is worth keeping, since I have no interest in descending that rabbit hole
+or fighting such accusations. Generally, going to the strongest possible
+argument, when requesting a change, is not actually your best move.
+
+Closing this bug report.
+"""]]