not a bug

2 files changed, 21 insertions, 0 deletions

diff --git a/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull.mdwn b/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull.mdwn
index 01153faad..8dcf3b6fc 100644
--- a/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull.mdwn
+++ b/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull.mdwn
@@ -32,3 +32,4 @@ $> echo MD5E-s11--74d80f7dsd99b835e5189948c8d4297efdsdfsdf | git annex dropkey -
 
 [[!meta author=yoh]]
 
+> [[notabug|done]] --[[Joey]]
diff --git a/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment b/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment
new file mode 100644
index 000000000..4e22e90ce
--- /dev/null
+++ b/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-05-03T17:03:25Z"
+ content="""
+Note that dropkey does *not* check if other copies exist, so the --force is
+unncessary; eg it's always forced by default.
+
+Anyway, dropkey will indicate a failure if it's actually unable to drop the
+content for some reason, eg a permissions problem or the content is locked
+to prevent it being dropped right now, or other unanticipated error.
+But, if the content of the key is not present, it's successfully
+gotten the repo into the requested state.
+
+Similarly, git-annex transferkey will return success if the key it was
+supposed to download is already present.
+
+I don't consider this a bug, although am willing to be convinced
+otherwise..
+"""]]