From f9d24e92a00de74eba952757514ace26b57c0698 Mon Sep 17 00:00:00 2001
From: "gioele@678b7c03f524f2669b179b603f65352fcc16774e" <gioele@web>
Date: Sat, 1 Apr 2023 11:09:49 +0000
Subject: [PATCH] Added a comment

---
 ..._c7c210961b51a87770932f40a9563622._comment | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_8_c7c210961b51a87770932f40a9563622._comment

diff --git a/doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_8_c7c210961b51a87770932f40a9563622._comment b/doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_8_c7c210961b51a87770932f40a9563622._comment
new file mode 100644
index 0000000000..c07046dbbe
--- /dev/null
+++ b/doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_8_c7c210961b51a87770932f40a9563622._comment
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="gioele@678b7c03f524f2669b179b603f65352fcc16774e"
+ nickname="gioele"
+ avatar="http://cdn.libravatar.org/avatar/366dbda84e78aff8a8a070622aeb63ce"
+ subject="comment 8"
+ date="2023-04-01T11:09:49Z"
+ content="""
+<hr/>
+
+> Anyway, 038a2600f4cf71294976280c5c29f6710359375f avoids it with a detached head.
+
+With git-annex 10.20230329-g30d7f9ad7 I got the following message after checking out `adjusted/master(unlockpresent)` and running `git annex copy --from foo --to bar -J2`:
+
+```
+git-annex: .git/HEAD: openFile: resource busy (file is locked)\"
+```
+
+This message appeared at the very end of the `copy` process.
+
+Regardless of this, everything seems to work just fine.
+
+"""]]