96853cd833
CONNECT is not supported by git-annex-shell p2pstdio, but for proxying to tor-annex remotes, it will be supported, and will make a git pull/push to a proxied remote work the same with that as it does over ssh, eg it accesses the proxy's git repo not the proxied remote's git repo. The p2p protocol docs say that NOTIFYCHANGES is not always supported, and it looked annoying to implement it for this, and it also seems pretty useless, so make it be a protocol error. git-annex remotedaemon will already be getting change notifications from the proxy's git repo, so there's no need to get additional redundant change notifications for proxied remotes that would be for changes to the same git repo. |
||
|---|---|---|
| .. | ||
| adjusted_branches | ||
| assistant | ||
| balanced_preferred_content | ||
| encryption | ||
| exporting_trees_to_special_remotes | ||
| external_backend_protocol | ||
| external_special_remote_protocol | ||
| git-remote-daemon | ||
| iabackup | ||
| metadata | ||
| new_repo_versions | ||
| p2p_protocol | ||
| requests_routing | ||
| adjusted_branches.mdwn | ||
| assistant.mdwn | ||
| balanced_preferred_content.mdwn | ||
| caching_database.mdwn | ||
| encryption.mdwn | ||
| exporting_trees_to_special_remotes.mdwn | ||
| external_backend_protocol.mdwn | ||
| external_special_remote_protocol.mdwn | ||
| gcrypt.mdwn | ||
| git-remote-daemon.mdwn | ||
| iabackup.mdwn | ||
| importing_trees_from_special_remotes.mdwn | ||
| metadata.mdwn | ||
| new_repo_versions.mdwn | ||
| p2p_protocol.mdwn | ||
| p2p_protocol_over_http.mdwn | ||
| passthrough_proxy.mdwn | ||
| preferred_content.mdwn | ||
| requests_routing.mdwn | ||
| roadmap.mdwn | ||