From 1409a44f9cc827c52c53fc1a0703a202507114a2 Mon Sep 17 00:00:00 2001 From: "richih@50508f31e0ee95720acd0120e16d6bdcad9d104b" Date: Tue, 10 Apr 2018 15:49:35 +0000 Subject: [PATCH] Added a comment --- ...ment_3_491d81f636a4da1deefd2d82063e2f05._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/move_violates_numcopies/comment_3_491d81f636a4da1deefd2d82063e2f05._comment diff --git a/doc/bugs/move_violates_numcopies/comment_3_491d81f636a4da1deefd2d82063e2f05._comment b/doc/bugs/move_violates_numcopies/comment_3_491d81f636a4da1deefd2d82063e2f05._comment new file mode 100644 index 0000000000..34abb9ff8b --- /dev/null +++ b/doc/bugs/move_violates_numcopies/comment_3_491d81f636a4da1deefd2d82063e2f05._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="richih@50508f31e0ee95720acd0120e16d6bdcad9d104b" + nickname="richih" + avatar="http://cdn.libravatar.org/avatar/499771047201f3eb29a462897b50a5f3" + subject="comment 3" + date="2018-04-10T15:49:35Z" + content=""" +I agree with anarcat. + +The core use case of git-annex is to maintain sets of known-good data. This function mainly relies on a directory structure, checksums, a defined minimum of copies, and tracking where they are. I would never have assumed that I would be able to get git-annex to go below the mincopies, at least not unless I was deep into the innards of git-annex and/or abusing --force or the like. + +-- RichiH +"""]]