mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
wolf480@8ad1ccdd08efc303a88f7e88c4e629be6637a44e 2023-04-01 07:23:18 +00:00 committed by admin
parent 45eaf8e484
commit 71e0ec2901
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/bugs/external_remote_export_sent_to_wrong_process/comment_7_6a85fcfa3eb0b4974733a62bcc0bbab2._comment Normal file
View file

@ -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?
"""]]