From 8b88dcf961f91184039b449973296562e071efc0 Mon Sep 17 00:00:00 2001 From: lh Date: Mon, 9 May 2022 19:18:01 +0000 Subject: [PATCH] Added a comment --- .../comment_4_a93d502253cf9f164fbcd23ca755db9d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d._comment 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 index 0000000000..87af99bb23 --- /dev/null +++ b/doc/forum/Issues_with_non-sync_workflow/comment_4_a93d502253cf9f164fbcd23ca755db9d._comment @@ -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. +"""]]