Added a comment
authorfalsifian <falsifian@web>
Tue, 5 Oct 2021 20:55:32 +0000 (20:55 +0000)
committeradmin <admin@branchable.com>
Tue, 5 Oct 2021 20:55:32 +0000 (20:55 +0000)
doc/forum/config_to_make_git_annex_sync_only_sync_metadata__63__/comment_2_11b9261bc5c32d3e36357afc021ac4e1._comment [new file with mode: 0644]

diff --git a/doc/forum/config_to_make_git_annex_sync_only_sync_metadata__63__/comment_2_11b9261bc5c32d3e36357afc021ac4e1._comment b/doc/forum/config_to_make_git_annex_sync_only_sync_metadata__63__/comment_2_11b9261bc5c32d3e36357afc021ac4e1._comment
new file mode 100644 (file)
index 0000000..ec390af
--- /dev/null
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="falsifian"
+ avatar="http://cdn.libravatar.org/avatar/59c3c23c500d20d83ecb9d1f149be9ae"
+ subject="comment 2"
+ date="2021-10-05T20:55:32Z"
+ content="""
+Thanks joey, your script is useful and I can use it as a workaround if necessary.
+
+I still don't understand the reason behind the behaviour. Why does `annex.synconlyannex = true` cause content to be synced? Wouldn't it be simpler to just say content is synced iff `annex.synccontent` is set to true? (I leave at the default, `false`, because I don't want content to be synced, but that does not help.)
+
+"""]]