summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar divB <divB@web>2014-07-17 04:53:08 +0000
committerGravatar admin <admin@branchable.com>2014-07-17 04:53:08 +0000
commitc8295b7d487307a4873d77132a5abf45740f53c4 (patch)
treedd27211d9e39b30a9ccc1789ca82792bcf81c9d0
parentd7093ccad2fe1c0bf7ee52bf1e2dc96ef177709b (diff)
-rw-r--r--doc/forum/Standard_groups__47__preferred_contents.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/forum/Standard_groups__47__preferred_contents.mdwn b/doc/forum/Standard_groups__47__preferred_contents.mdwn
new file mode 100644
index 000000000..89e2b848c
--- /dev/null
+++ b/doc/forum/Standard_groups__47__preferred_contents.mdwn
@@ -0,0 +1,14 @@
+Sorry that I am not stop asking questions - I am trying to wrap my head around annex still - and I do not fully understand the standard groups/preferred contents yet.
+
+
+First, basic: Is the "preferred content group" an attribute of a repository or of a remote? E.g., when I use assistant, I can set this property for a *remote* repository. Will this property be synced to all other clients then or is it only valid for this particular client?
+
+Second, I think the standard groups do still not cover what I want and I wonder if this could be done with preferred contents somehow? What I want:
+
+* Generally only the structure should be synced, no contents (i.e. "manual" is the closest)
+
+* When I (manually) do "git annex get" on a file this file should be synced whenever it changes locally *or* remotely (until I drop it again). Currently it seems that when it changes remotely, it is "dropped" again so I need to manually use "git annex get" again
+
+* When I (manually) do "git annex get" on a directory, it should be (recursively) synced whenever it or any file changes locally or remotely (until I drop it again). Currently nothing seems to sync at all in this case (except the meta data)
+
+Thanks!