From fddf14600bc8867dcae168986eb47b977404c5e4 Mon Sep 17 00:00:00 2001 From: anarcat Date: Tue, 10 Apr 2018 14:20:08 +0000 Subject: [PATCH] Added a comment: force? --- ...comment_2_57299719a6e8f3615819da4fbc460da5._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/move_violates_numcopies/comment_2_57299719a6e8f3615819da4fbc460da5._comment diff --git a/doc/bugs/move_violates_numcopies/comment_2_57299719a6e8f3615819da4fbc460da5._comment b/doc/bugs/move_violates_numcopies/comment_2_57299719a6e8f3615819da4fbc460da5._comment new file mode 100644 index 0000000000..178164c811 --- /dev/null +++ b/doc/bugs/move_violates_numcopies/comment_2_57299719a6e8f3615819da4fbc460da5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="anarcat" + avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7" + subject="force?" + date="2018-04-10T14:20:08Z" + content=""" +This definitely seems strange to me. i've been using git-annex for a long time, and I have never known `move` was unsafe by default. so I think that `--safe` should definitely be made defautl. + +but beyond that, I wouldn't use `--unsafe` as a new flag: we already have `--force` for `--drop` for example, shouldn't we reuse that here as well? +"""]]