diff options
| -rw-r--r-- | doc/forum/Multiple_prefered_content_groups/comment_1_b401d234c0730412053f0f6a6f9cf2d6._comment | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/forum/Multiple_prefered_content_groups/comment_1_b401d234c0730412053f0f6a6f9cf2d6._comment b/doc/forum/Multiple_prefered_content_groups/comment_1_b401d234c0730412053f0f6a6f9cf2d6._comment new file mode 100644 index 000000000..f47fe5eef --- /dev/null +++ b/doc/forum/Multiple_prefered_content_groups/comment_1_b401d234c0730412053f0f6a6f9cf2d6._comment @@ -0,0 +1,32 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-07-11T16:39:44Z" + content=""" +What git-annex actually does when a repository is in multiple groups +is that the "standard" preferred content expression has no effect. +Because this is an ambiguous configuration and it's not clear what you +want. + +I don't think that you can combine preferred content expressions for +multiple groups and always get behavior that makes sense. In particular, +it seems likely that in some situations you'd want to combine them with AND +but in other situations with OR. + +So, the best thing for you to do is probably to manually write a preferred +content expression that clearly expresses what you want. Note that you +can have a repository that's in the archive group, but instead of "standard" +has its own custom preferred content expression. In your case, I think you +want to do that; keeping the repository in the archive group will retain +the behavior of other repositories dropping archived files once they reach +it. + +Seems that for the preferred content setting for this repositry, you +want the same one used for backup repositories, "anything". + +So: + + git annex group . archive + git annex ungroup . backup + git anenx wanted . anything +"""]] |