comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 4 Apr 2023 18:31:25 +0000 (14:31 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 4 Apr 2023 18:31:25 +0000 (14:31 -0400)
doc/bugs/external_remote_export_sent_to_wrong_process/comment_8_c4610009f691ce60940979b73bef4d78._comment [new file with mode: 0644]

diff --git a/doc/bugs/external_remote_export_sent_to_wrong_process/comment_8_c4610009f691ce60940979b73bef4d78._comment b/doc/bugs/external_remote_export_sent_to_wrong_process/comment_8_c4610009f691ce60940979b73bef4d78._comment
new file mode 100644 (file)
index 0000000..97fc92b
--- /dev/null
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 8"""
+ date="2023-04-04T18:26:29Z"
+ content="""
+You would not need to send back `EXTENSIONS PROTOCOLVERSION2`
+yourself, only check if git-annex sends it. A better name might be 
+EXPORTBUGFIXED, it's only using the existing extensions mechanism as a flag
+to communicate that git-annex has the bug fixed.
+
+Some old versions of git-annex don't send EXTENSIONS at all (and those
+also don't have the bug fixed), but if git-annex does send it, it will
+always be before EXPORTSUPPORTED.
+"""]]