update

diff --git a/doc/todo/git-annex_proxies.mdwn b/doc/todo/git-annex_proxies.mdwn
index 2b779b5c17a8d304b0bf8d9f03b5ebaa4007ca96..0ad17a00b4c78d6bd1fa8155c2be9b5b7b6709cb 100644 (file)
--- a/doc/todo/git-annex_proxies.mdwn
+++ b/doc/todo/git-annex_proxies.mdwn
@@ -24,49 +24,17 @@ Planned schedule of work:
 
 In development on the `proxy` branch.
 
-For June's work on [[design/passthrough_proxy]], implementation plan:
-
-* UUID discovery via git-annex branch. Add a log file listing UUIDs
-  accessible via proxy UUIDs. It also will contain the names
-  of the remotes that the proxy is a proxy for, 
-  from the perspective of the proxy. (done)
-
-* Add `git-annex updateproxy` command (done)
-
-* Remote instantiation for proxies. (done)
-
-* Implement git-annex-shell proxying to git remotes. (done)
-
-* Proxy should update location tracking information for proxied remotes,
-  so it is available to other users who sync with it. (done)
-
-* Implement `git-annex updatecluster` command (done)
-
-* Implement cluster UUID insertation on location log load, and removal
-  on location log store. (done)
-
-* Omit cluster UUIDs when constructing drop proofs, since lockcontent will
-  always fail on a cluster. (done)
-
-* Don't count cluster UUID as a copy. (done)
-
-* Tab complete proxied remotes and clusters in eg --from option. (done)
-
-* Getting a key from a cluster should proxy from one of the nodes that has
-  it. (done)
-
-* Implement upload with fanout and reporting back additional UUIDs over P2P
-  protocol. (done)
-
-* Implement cluster drops, trying to remove from all nodes, and returning
-  which UUIDs it was dropped from. (done)
+For June's work on [[design/passthrough_proxy]], remaining todos:
 
 * `git-annex sync --content` does not send content to clusters, or to
   proxied remotes. Seems that the second call to Remote.list somehow
   is failing to listProxies. 
 
-* `git-annex sync` etc, when operating on clusters, should operate on the
-  cluster as a whole, not on cluster nodes.
+* `git-annex sync` etc, when operating on clusters, should first 
+  operate on the cluster as a whole, to take advantages of fanout on upload
+  and mass drop. Only operate on individual cluster nodes afterwards,
+  to handle cases such as a cluster containing a key, but some node
+  wanting and lacking the key.
 
 * On upload to cluster, send to nodes where it's preferred content, and not
   to other nodes.
@@ -109,3 +77,43 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
 
 * `viconfig` support for setting preferred content, group, 
   and description of clusters
+
+
+# completed items for June's work on [[design/passthrough_proxy]]:
+
+* UUID discovery via git-annex branch. Add a log file listing UUIDs
+  accessible via proxy UUIDs. It also will contain the names
+  of the remotes that the proxy is a proxy for, 
+  from the perspective of the proxy. (done)
+
+* Add `git-annex updateproxy` command (done)
+
+* Remote instantiation for proxies. (done)
+
+* Implement git-annex-shell proxying to git remotes. (done)
+
+* Proxy should update location tracking information for proxied remotes,
+  so it is available to other users who sync with it. (done)
+
+* Implement `git-annex updatecluster` command (done)
+
+* Implement cluster UUID insertation on location log load, and removal
+  on location log store. (done)
+
+* Omit cluster UUIDs when constructing drop proofs, since lockcontent will
+  always fail on a cluster. (done)
+
+* Don't count cluster UUID as a copy in numcopies checking etc. (done)
+
+* Tab complete proxied remotes and clusters in eg --from option. (done)
+
+* Getting a key from a cluster should proxy from one of the nodes that has
+  it. (done)
+
+* Implement upload with fanout to multiple cluster nodes and reporting back
+  additional UUIDs over P2P protocol. (done)
+
+* Implement cluster drops, trying to remove from all nodes, and returning
+  which UUIDs it was dropped from. (done)
+
+* `git-annex testremote` works against proxied remote and cluster. (done)