From b8a03643e5f6bd35538abb1fb7b18e68c671e321 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 19 May 2023 18:47:49 +0000 Subject: [PATCH] Added a comment --- .../comment_3_52f21e094853f787c18f4b9737d9771f._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/dropkey_-z_does_not_drop_etc/comment_3_52f21e094853f787c18f4b9737d9771f._comment diff --git a/doc/bugs/dropkey_-z_does_not_drop_etc/comment_3_52f21e094853f787c18f4b9737d9771f._comment b/doc/bugs/dropkey_-z_does_not_drop_etc/comment_3_52f21e094853f787c18f4b9737d9771f._comment new file mode 100644 index 0000000000..cdbbc90768 --- /dev/null +++ b/doc/bugs/dropkey_-z_does_not_drop_etc/comment_3_52f21e094853f787c18f4b9737d9771f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 3" + date="2023-05-19T18:47:49Z" + content=""" +It makes total sense, thank you Joey! I guess a little odd behavior is only the reporting of git annex `ok` for dropping an unknown key. I guess like with `rm unknownfile` (unless `-f` is used) I would have expected it to error out. +"""]] -- 2.30.2