From c69a3bd842fcf2613fabcf7660218a23af61c5ce Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 19 Apr 2022 12:40:17 -0400 Subject: [PATCH] comment --- ...comment_1_99f89201446005f77d9278a7a889638d._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Issues_with_non-sync_workflow/comment_1_99f89201446005f77d9278a7a889638d._comment diff --git a/doc/forum/Issues_with_non-sync_workflow/comment_1_99f89201446005f77d9278a7a889638d._comment b/doc/forum/Issues_with_non-sync_workflow/comment_1_99f89201446005f77d9278a7a889638d._comment new file mode 100644 index 0000000000..9265f1caaa --- /dev/null +++ b/doc/forum/Issues_with_non-sync_workflow/comment_1_99f89201446005f77d9278a7a889638d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-04-19T16:28:06Z" + content=""" +I don't think anything git-annex can do would make git worktree behave the +way you want it to behave, except for a whole separate mode of operation +that writes to the git-annex branch via writing to the worktree for it and +committing. +"""]]