better indicate when special remotes do not support renameExport

Avoid a warning message when renameExport is not supported, and just
fallback to deleting with a subsequent re-upload. Especially needed for
importtree remotes, where renameExport needs to be disabled.

This changes the external special remote protocol, but in a
backwards-compatible way. A reply of UNSUPPORTED-REQUEST to an older
version of git-annex will cause it to make renameExport return False.
This commit is contained in:
Joey Hess 2019-03-11 12:44:12 -04:00
parent c755788256
commit 2912429640
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
11 changed files with 62 additions and 53 deletions

View file

@ -10,10 +10,6 @@ this.
## implementation notes
* renameExport is disabled in a way that makes export tree
complain unncessarily verbosely. Perhaps change renameExport
to a Maybe so it can know when it's not available.
* Does export of master:subdir update the remote tracking branch right?
* Does sync --content with remote.name.annex-tracking-branch=master:subdir