From f2914ab6a0ae15b331751075dfddd84d4b0a2e36 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 31 Mar 2023 13:11:35 -0400 Subject: [PATCH] idea --- .../comment_6_e38b776c73affdbb06f3debdddb07e59._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/external_remote_export_sent_to_wrong_process/comment_6_e38b776c73affdbb06f3debdddb07e59._comment diff --git a/doc/bugs/external_remote_export_sent_to_wrong_process/comment_6_e38b776c73affdbb06f3debdddb07e59._comment b/doc/bugs/external_remote_export_sent_to_wrong_process/comment_6_e38b776c73affdbb06f3debdddb07e59._comment new file mode 100644 index 0000000000..de7cd4053d --- /dev/null +++ b/doc/bugs/external_remote_export_sent_to_wrong_process/comment_6_e38b776c73affdbb06f3debdddb07e59._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2023-03-31T16:55:49Z" + content=""" +What if I made git-annex send "EXTENSIONS PROTOCOLVERSION2"? Then +you could reply to EXPORTSUPPORTED with EXPORTSUPPORTED-FAILURE +when used by a buggy git-annex. +"""]]