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

Added a comment

Browse source
This commit is contained in:
wolf480@8ad1ccdd08efc303a88f7e88c4e629be6637a44e 2023-03-30 17:33:10 +00:00 committed by admin
parent 51643bba3e
commit 43878157d3
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/external_remote_export_sent_to_wrong_process/comment_4_db89603335995755d145141705ac4584._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="wolf480@8ad1ccdd08efc303a88f7e88c4e629be6637a44e"
nickname="wolf480"
avatar="http://cdn.libravatar.org/avatar/816b19ee786208f3216fe146d7733086"
subject="comment 4"
date="2023-03-30T17:33:10Z"
content="""
Hmm but a remote only learns that it's being used with exporttree=yes *after* it has sent a `VERSION`?
I'm afraid I can't bump the version in case of git-annex-remote-rclone, it's already widely used for non-exporttree scenarios and requiring a git-annex that supports `VERSION 2` for these existing usecases (which aren't affected by this bug) would be a regression...
I'll ask git-annex-remote-rclone maintainers, but it seems to me that defensive coding around the `EXPORT` command is gonna be a better solution in this remote's case.
"""]]