From dddad6181f3430f47656ff9e143cf1a0a9baddda Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 14 Oct 2012 16:01:16 -0400 Subject: handle transfer repository bootstrapping When there's just 1 client repo, and a transfer repo is created, its preferred content will now make it prefer all content in the client, even though there's no other client yet to transfer it to. Presumably, another client will be created eventually. It might even already exist, and the transfer repo will be used to connect up with it. --- doc/preferred_content.mdwn | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc/preferred_content.mdwn') diff --git a/doc/preferred_content.mdwn b/doc/preferred_content.mdwn index c130a07e6..6205eb4c9 100644 --- a/doc/preferred_content.mdwn +++ b/doc/preferred_content.mdwn @@ -61,7 +61,13 @@ USB drive used in a sneakernet. The preferred content expression for these causes them to get and retain data until all clients have a copy. -`not inallgroup=client and exclude=*/archive/*` +`not (inallgroup=client or not copies=client:2) and exclude=*/archive/*` + +The "not copies=client:2" part of the above handles the case where +there is only one client repository. It makes a transfer repository +speculatively prefer content in this case, even though it as of yet +has nowhere to transfer it to. Presumably, another client repository +will be added later. ### archive -- cgit v1.2.3