diff options
Diffstat (limited to 'doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment')
| -rw-r--r-- | doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment | 20 |
1 files changed, 0 insertions, 20 deletions
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 deleted file mode 100644 index 4e22e90ce..000000000 --- a/doc/bugs/dropkey_--batch_--json_--force_is_always_succesfull/comment_1_b913175c341d39e6b9d354213677248c._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!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.. -"""]] |