summaryrefslogtreecommitdiff
path: root/doc/preferred_content
diff options
context:
space:
mode:
authorGravatar grawity@2ea26be48562f66fcb9b66307da72b1e2e37453f <grawity@web>2016-01-28 09:32:45 +0000
committerGravatar admin <admin@branchable.com>2016-01-28 09:32:45 +0000
commit8e5f680660ab9f786100155009a8fdadd2c4ac28 (patch)
tree573f1347c1571f6c26e52f247c1c06ad35986e99 /doc/preferred_content
parent40c57cb96c29d4a40b3fcdb3428f82b46f9ddab2 (diff)
Added a comment: default settings?
Diffstat (limited to 'doc/preferred_content')
-rw-r--r--doc/preferred_content/comment_10_d9eb7d8efe731cbcdb456fc56935d886._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/preferred_content/comment_10_d9eb7d8efe731cbcdb456fc56935d886._comment b/doc/preferred_content/comment_10_d9eb7d8efe731cbcdb456fc56935d886._comment
new file mode 100644
index 000000000..c7a898c68
--- /dev/null
+++ b/doc/preferred_content/comment_10_d9eb7d8efe731cbcdb456fc56935d886._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="grawity@2ea26be48562f66fcb9b66307da72b1e2e37453f"
+ nickname="grawity"
+ subject="default settings?"
+ date="2016-01-28T09:32:45Z"
+ content="""
+Could you clarify how the _default_ (empty) preferred content setting works? Is it equivalent to `anything`, or more magical than that?
+
+(Asking because I noticed that `annex find --in . --want-drop` in such a repo matches basically all files, even the ones that `annex sync --content` just retrieved. Likewise, it retrieves files while `annex find --not --in . --want-get` lists nothing. I'm fine with the sync behavior here, but somewhat worried that a _future_ `annex sync --content` would actually decide to drop everything... I'm running 6.20160126 with numcopies=1.)
+
+Also, what happens if I use `standard` for a repo that's not in any group?
+"""]]