From e3a58a271088250b58a8e057e3cae8ac58115ffc Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Tue, 9 Apr 2024 10:48:10 +0000 Subject: [PATCH] Added a comment: or use numcopies for safety --- .../comment_3_19e77a51911d3c2d39a558162223e78e._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/Idea_for_emulating_a_versioned_tree_export/comment_3_19e77a51911d3c2d39a558162223e78e._comment diff --git a/doc/todo/Idea_for_emulating_a_versioned_tree_export/comment_3_19e77a51911d3c2d39a558162223e78e._comment b/doc/todo/Idea_for_emulating_a_versioned_tree_export/comment_3_19e77a51911d3c2d39a558162223e78e._comment new file mode 100644 index 0000000000..2968adabb7 --- /dev/null +++ b/doc/todo/Idea_for_emulating_a_versioned_tree_export/comment_3_19e77a51911d3c2d39a558162223e78e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="or use numcopies for safety" + date="2024-04-09T10:48:10Z" + content=""" +Or, even better: If such an export action would cause data loss, the potentially vanishing keys would be known, because they reside in a git-tree that you diff anyway, right? Git annex could then apply its usual logic of 'I shall never execute an action that reduces a file's copies below `$numcopies`' and error out with an explanation. That feels right and consistent with git annex' typical behavior. +"""]]