From: lh <lh@web>
Date: Tue, 19 Apr 2022 18:15:53 +0000 (+0000)
Subject: Added a comment
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~75^2~39
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=8f11d1a43b64ad181383a3499e456e76777655cc;p=git-annex.git

Added a comment
---

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
index 0000000000..9b4b04a62e
--- /dev/null
+++ b/doc/forum/Issues_with_non-sync_workflow/comment_2_f27ec2462e5a8f6f96c6e2b7dd3f87ca._comment
@@ -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.
+"""]]