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

avoid trying to export tree to proxied exporttree=yes remotes

Browse source 
This avoids a lot of ugly messages when syncing with such a remote.
The export tree happens on the proxy side.
This commit is contained in:
Joey Hess 2024-08-07 13:00:19 -04:00
parent 6d96734128
commit 55adbb6694
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 18 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/todo/git-annex_proxies.mdwn
View file

@ -33,13 +33,8 @@ Planned schedule of work:
* Working on `exportreeplus` branch which is groundwork for proxying to
exporttree=yes special remotes. Need to merge it to master.
* `git-annex sync --content` now updates a proxied exporttree=yes special
remote! But, there are some messages like these that should be avoided:
Not updating export to origin-d to reflect changes to the tree, because export tracking is not enabled. (Set remote.origin-d.annex-tracking-branch to enable it.)
export origin-d 1
export not supported
failed
* `git-annex sync` hides output of git-annex post-retreive, which is a
problem when it's doing things that are expensive.
* Handle cases where a single key is used by multiple files in the exported
tree. Need to download from the special remote in order to export
@ -47,6 +42,11 @@ Planned schedule of work:
`git-annex push`. When using first `git push` followed by
`git-annex copy --to` the proxied remote, the received key is stored
to all export locations.)
* Implement `git-annex export treeish --to=foo --from=bar`, which
gets from bar as needed to send to foo. Make post-retrieve use
`--to=r --from=r` to handle the multiple files case.
* Handle case where the special remote does not support renameExport.
Each key will need to be downloaded from it in order to export the key
back to it, if the proxy is to support such a remote.