Added a comment
authorlh <lh@web>
Tue, 19 Apr 2022 18:15:53 +0000 (18:15 +0000)
committeradmin <admin@branchable.com>
Tue, 19 Apr 2022 18:15:53 +0000 (18:15 +0000)
doc/forum/Issues_with_non-sync_workflow/comment_2_f27ec2462e5a8f6f96c6e2b7dd3f87ca._comment [new file with mode: 0644]

diff --git a/doc/forum/Issues_with_non-sync_workflow/comment_2_f27ec2462e5a8f6f96c6e2b7dd3f87ca._comment b/doc/forum/Issues_with_non-sync_workflow/comment_2_f27ec2462e5a8f6f96c6e2b7dd3f87ca._comment
new file mode 100644 (file)
index 0000000..9b4b04a
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="lh"
+ avatar="http://cdn.libravatar.org/avatar/d31bade008d7da493d9bfb37d68fd825"
+ subject="comment 2"
+ date="2022-04-19T18:15:53Z"
+ content="""
+But the worktree won't confuse git-annex in any way, right?
+
+If that's the case, I guess I'll just remember to hard reset the worktree every time I want to work with it. As long as git-annex doesn't ever leave things uncommitted on its branch, that should be fine.
+"""]]