From a3fa146be49bff61e040eb0ae8eaf3c0feca583c Mon Sep 17 00:00:00 2001 From: CandyAngel Date: Tue, 10 Apr 2018 10:39:23 +0000 Subject: [PATCH] Added a comment --- ...comment_1_36e22ecc569f097e4cc58c20d0fa4876._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/move_violates_numcopies/comment_1_36e22ecc569f097e4cc58c20d0fa4876._comment diff --git a/doc/bugs/move_violates_numcopies/comment_1_36e22ecc569f097e4cc58c20d0fa4876._comment b/doc/bugs/move_violates_numcopies/comment_1_36e22ecc569f097e4cc58c20d0fa4876._comment new file mode 100644 index 0000000000..d59c6ead8a --- /dev/null +++ b/doc/bugs/move_violates_numcopies/comment_1_36e22ecc569f097e4cc58c20d0fa4876._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="CandyAngel" + avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8" + subject="comment 1" + date="2018-04-10T10:39:23Z" + content=""" +If git-annex knows it isn't going to do what I've instructed (move the file), I think it should just fail the command immediately, rather than copying but not dropping. + +You could make *--safe* fallback to copy (for those that want that behaviour) and *--unsafe* has the risky behaviour, but *move* should either do just that, move the file, or do nothing. +"""]]