aboutsummaryrefslogtreecommitdiff
path: root/Types/StandardGroups.hs
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-10-14 16:01:16 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-10-14 16:08:21 -0400
commitdddad6181f3430f47656ff9e143cf1a0a9baddda (patch)
tree70f4d35943f768ac599064a3c51731426a31d9f0 /Types/StandardGroups.hs
parenta4fe8365f3745033a307817e754f132357af47f7 (diff)
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.
Diffstat (limited to 'Types/StandardGroups.hs')
-rw-r--r--Types/StandardGroups.hs2
1 files changed, 1 insertions, 1 deletions
diff --git a/Types/StandardGroups.hs b/Types/StandardGroups.hs
index 32e2cb3af..aeae200c2 100644
--- a/Types/StandardGroups.hs
+++ b/Types/StandardGroups.hs
@@ -32,6 +32,6 @@ descStandardGroup BackupGroup = "backup: collects all files"
{- See doc/preferred_content.mdwn for explanations of these expressions. -}
preferredContent :: StandardGroup -> String
preferredContent ClientGroup = "exclude=*/archive/*"
-preferredContent TransferGroup = "not inallgroup=client and " ++ preferredContent ClientGroup
+preferredContent TransferGroup = "not (inallgroup=client or not copies=client:2) and " ++ preferredContent ClientGroup
preferredContent ArchiveGroup = "not copies=archive:1"
preferredContent BackupGroup = "" -- all content is preferred