diff --git a/doc/bugs/move_violates_numcopies/comment_4_370ab3e7adbe6f1888eb5ebe542d18ad._comment b/doc/bugs/move_violates_numcopies/comment_4_370ab3e7adbe6f1888eb5ebe542d18ad._comment
new file mode 100644
index 0000000000..68fda3b6a9
--- /dev/null
+++ b/doc/bugs/move_violates_numcopies/comment_4_370ab3e7adbe6f1888eb5ebe542d18ad._comment
@@ -0,0 +1,21 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2018-04-10T17:04:14Z"
+ content="""
+Candyangel, thanks, failing is indeed the better thing to do
+than copying when it's not safe to move. That makes sense.
+
+Also, `git annex move` should honor required contents, and refuse to move
+content away from a repository that requires it.
+
+It would be ok to use --force instead of --unsafe, but it doesn't allow for
+a staged transition from --unsafe by default to --safe by default. But, if
+we decide a stanged transition is not needed, I would be inclined to use
+the --force.
+
+Move failing in these situations seems less likely to badly break existing
+workflows than move leaving both copies would; the caller will see
+that git-annex errored, rather than it silently leaving extra copies.
+So perhaps a staged transition could be skipped.
+"""]]