From bd8481b23d0c85b1a9017dc6390fcb548d2e8d49 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 25 Feb 2020 12:46:01 -0400 Subject: [PATCH] comment --- ..._2e768899c332cacffcb1fa6edb195325._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_12_2e768899c332cacffcb1fa6edb195325._comment diff --git a/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_12_2e768899c332cacffcb1fa6edb195325._comment b/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_12_2e768899c332cacffcb1fa6edb195325._comment new file mode 100644 index 0000000000..017634efd3 --- /dev/null +++ b/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_12_2e768899c332cacffcb1fa6edb195325._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 12""" + date="2020-02-25T16:31:55Z" + content=""" +Generally, command-line options should override other configuration, +so --only-annex seems like it should enable content syncing even if +annex.synccontent=false were a documented setting, the same as --content +should. + +I think a case could be made for annex.synccontent=false + +annex.synconlyannex=true not syncing content. + +I do wonder though if that's the best approach. It kind of seems like what +you really want is a way to configure a default preferred content +expression for clones that do not have a specific one configured. And +that seems more broadly useful than fine-tuning the interaction of two +git-annex sync configurations. +"""]]