Added a comment
authorlh <lh@web>
Mon, 9 May 2022 19:18:01 +0000 (19:18 +0000)
committeradmin <admin@branchable.com>
Mon, 9 May 2022 19:18:01 +0000 (19:18 +0000)
doc/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d._comment [new file with mode: 0644]

diff --git a/doc/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d._comment b/doc/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d._comment
new file mode 100644 (file)
index 0000000..87af99b
--- /dev/null
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="lh"
+ avatar="http://cdn.libravatar.org/avatar/d31bade008d7da493d9bfb37d68fd825"
+ subject="comment 4"
+ date="2022-05-09T19:18:01Z"
+ content="""
+Still curious about how `annex.alwayscommit=false` tracks modifications and whether mucking with a `git-annex` worktree could cause data loss with this option enabled.
+"""]]