update

diff --git a/doc/design/passthrough_proxy.mdwn b/doc/design/passthrough_proxy.mdwn
index acae91a7cbfc25a858f5f1395acd7bdfd9514894..6b8d5e6db872e83a71106f3745210667405b3214 100644 (file)
--- a/doc/design/passthrough_proxy.mdwn
+++ b/doc/design/passthrough_proxy.mdwn
@@ -130,6 +130,24 @@ prefer, that points at a remote behind a proxy. They just need to set
 its annex-uuid and its url. Perhaps there should be a git-annex command
 that eases setting up a remote like that?
 
+## proxied remotes in git remote list
+
+Should instantiated remotes have enough configured in git so that
+`git remote list` will list them? This would make things like tab
+completion of proxied remotes work, and would generally let the user
+discover that there *are* proxied remotes.
+
+This could be done by a config like remote.name.annex-proxied = true.
+That makes other configs of the remote not prevent it being used as an
+instantiated remote. So remote.name.annex-uuid can be changed when
+the uuid behind a proxy changes. And it allows updating remote.name.url
+to keep it the same as the proxy remote's url. (Or possibly to set it to
+something else?)
+
+Configuring the instantiated remotes like that would let anyone who can
+write to the git-annex branch flood other people's repos with configs
+for any number of git remotes. Which might be obnoxious.
+
 ## user interface
 
 But the user probably doesn't want to pick which node to send content to.

diff --git a/doc/todo/git-annex_proxies.mdwn b/doc/todo/git-annex_proxies.mdwn
index 6bcc7cd0e58671f85cf6147c8158c8db63eee1bf..68213670b4ff218508ee6e1250641646a9e78725 100644 (file)
--- a/doc/todo/git-annex_proxies.mdwn
+++ b/doc/todo/git-annex_proxies.mdwn
@@ -41,14 +41,8 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
 * Proxy should update location tracking information for proxied remotes,
   so it is available to other users who sync with it. (done)
 
-* Would it be possible to get instantiated remotes into git remote list?
-  This would make eg, tab completion of remote names work. Just setting
-  annex-uuid would suffice, but currently any such config prevents setting
-  up a remote as an instantiated remote. Perhaps if only annex-uuid and no
-  other config is set, treat that as an instantiated remote, and overwrite
-  the annex-uuid config as necessaery? Or, add a config that says this is
-  an instanatiated remote, and when set, allow overwriting configs.
-  This seems better, it would let `git push proxy-foo` work, for example.
+* Consider getting instantiated remotes into git remote list.
+  See design.
 
 * Cycle prevention. See design.