diff --git a/doc/bugs/Importing__95__Commands__95__Destructive__95__by__95__default/comment_8_f24b544018d84b0182621d07bb9c8c3d._comment b/doc/bugs/Importing__95__Commands__95__Destructive__95__by__95__default/comment_8_f24b544018d84b0182621d07bb9c8c3d._comment
new file mode 100644
index 0000000000..f3e7a385fe
--- /dev/null
+++ b/doc/bugs/Importing__95__Commands__95__Destructive__95__by__95__default/comment_8_f24b544018d84b0182621d07bb9c8c3d._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="andrew"
+ avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
+ subject="comment 8"
+ date="2018-07-13T15:04:13Z"
+ content="""
+That all makes sense Joey/CandyAngel. I do wonder how this command will change though if [import tree](https://git-annex.branchable.com/todo/import_tree/) is ever implemented. I presume the default behavior of `git annex import treeish` would preserve the source tree as if the option `--duplicate` had been given? Whereas `git annex import path` would continue to move files by default. But maybe this is another reason not to do `git annex import treeish`, maybe that command should be `git annex importtree treeish`?
+
+In terms of the anonymous poster's suggestions of changing the options to import, I would say all of your suggestions already exist in a usable form “skip existing known files” is already an option `--skip-duplicates`, “--remove-source==never” is already an option `--duplicate` and presumably “--reinject-missing” is similar to the existing option `--force`.
+"""]]