update

diff --git a/doc/todo/git-annex_proxies.mdwn b/doc/todo/git-annex_proxies.mdwn
index e76b32fb5cc3d7de6975dfb56b42550c0ec4f06e..b3ffb080652748fce38a28d32a2c253e3e2b44c9 100644 (file)
--- a/doc/todo/git-annex_proxies.mdwn
+++ b/doc/todo/git-annex_proxies.mdwn
@@ -21,8 +21,8 @@ Planned schedule of work:
 * July: p2p protocol over http
 * August, part 1: git-annex proxy support for exporttree
 * August, part 2: balanced preferred content
-* September: streaming through proxy to special remotes (especially S3)
 * October: proving behavior of balanced preferred content with proxies
+* September: streaming through proxy to special remotes (especially S3)
 
 [[!tag projects/openneuro]]
 

diff --git a/doc/todo/proving_preferred_content_behavior.mdwn b/doc/todo/proving_preferred_content_behavior.mdwn
index b98166fadeb84eee5260413195a7f8d202f212ff..0b1f1fee0bfc3136a5987e963c3143de1ea976ce 100644 (file)
--- a/doc/todo/proving_preferred_content_behavior.mdwn
+++ b/doc/todo/proving_preferred_content_behavior.mdwn
@@ -35,18 +35,9 @@ matter the sizes of the underlying repositories, but balanced preferred
 content does take repository fullness into account, which further
 complicates fully understanding the behavior.
 
-Notice that `balanced()` (in the current design) is not stable when used
-on its own, and has to be used as part of a larger expression to make it
-stable, eg:
-
-    ((balanced(backup) and not (copies=backup:1)) or present
-
-So perhaps `balanced()` should include the other checks in it,
-to avoid the user shooting themselves in the foot. On the other 
-hand, if `balanced()` implicitly contains `present`, then `not balanced()`
-would include `not present`, which is bad!
-
-(For that matter, what does `not balanced()` even do currently?)
+Notice that `fullbalanced()` is not stable when used
+on its own, and so `balanced()` adds an "or present" to stabilize it.
+And so `not balanced()` includes `not present`, which is bad!
 
 ## proof