diff --git a/doc/bugs/external_remote_export_sent_to_wrong_process/comment_7_6a85fcfa3eb0b4974733a62bcc0bbab2._comment b/doc/bugs/external_remote_export_sent_to_wrong_process/comment_7_6a85fcfa3eb0b4974733a62bcc0bbab2._comment
new file mode 100644
index 0000000000..a633b3828a
--- /dev/null
+++ b/doc/bugs/external_remote_export_sent_to_wrong_process/comment_7_6a85fcfa3eb0b4974733a62bcc0bbab2._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="wolf480@8ad1ccdd08efc303a88f7e88c4e629be6637a44e"
+ nickname="wolf480"
+ avatar="http://cdn.libravatar.org/avatar/816b19ee786208f3216fe146d7733086"
+ subject="comment 7"
+ date="2023-04-01T07:23:18Z"
+ content="""
+So basically I'd reply to it with `EXTENSIONS PROTOCOLVERSION2`, and then set a flag that supporting export is ok?
+And `EXTENSIONS` always comes before `EXPORTSUPPORTED` ?
+Sounds like a very ad-hoc use of the extension mechanism... I think it'd work but I'd feel bad if you made a release with such a feature and then it turned out it doesn't work...
+Do you have some sort of per-releases?
+"""]]