diagnose user error

diff --git a/doc/bugs/external_remote_protocol_unable_to_parse_command.mdwn b/doc/bugs/external_remote_protocol_unable_to_parse_command.mdwn
index 19e27cf0dff284eafab69eb7dcba31acce01360d..2b15892c4ab6d9a91c0cacd8c9cd4302066df4bd 100644 (file)
--- a/doc/bugs/external_remote_protocol_unable_to_parse_command.mdwn
+++ b/doc/bugs/external_remote_protocol_unable_to_parse_command.mdwn
@@ -29,3 +29,5 @@ Have I misunderstood the protocol or is this a bug?
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
 I use git-annex successfully constantly and have done for years. :-) First time writing a special external remote, though.
+
+> [[notabug|done]] --[[Joey]]

diff --git a/doc/bugs/external_remote_protocol_unable_to_parse_command/comment_1_a10012aa7df76a2366ea40da8c37b798._comment b/doc/bugs/external_remote_protocol_unable_to_parse_command/comment_1_a10012aa7df76a2366ea40da8c37b798._comment
new file mode 100644 (file)
index 0000000..4dd1650
--- /dev/null
+++ b/doc/bugs/external_remote_protocol_unable_to_parse_command/comment_1_a10012aa7df76a2366ea40da8c37b798._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-03-21T17:17:54Z"
+ content="""
+"foo" is not a valid git-annex key, so "GETSTATE foo" is a protocol error.
+
+If you had it send "GETSTATE SHA256E-s19--3b99fd544e5e49915ca060f193c615caf82a045b1145672dd6f2181473fd516d",
+it would work.
+"""]]