probably fixed but I didn't actually reproduce it
authorJoey Hess <joeyh@joeyh.name>
Tue, 4 Apr 2023 18:25:55 +0000 (14:25 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 4 Apr 2023 18:25:55 +0000 (14:25 -0400)
doc/bugs/__34__.git__47__HEAD__58___openFile__58___resource_busy__34___after_copy.mdwn
doc/bugs/__34__.git__47__HEAD__58___openFile__58___resource_busy__34___after_copy/comment_2_399dcbe7f3772526efbe13bd5b13156d._comment [new file with mode: 0644]

index f1fd1c1a68ed76d2f3dd8c75ac2e974fb51dc9ab..96b21ca057a5c60ceb0c1de28a8fa9634c0eb6c0 100644 (file)
@@ -41,3 +41,4 @@ local repository version: 8
 
 This is probably related to [[bugs/Failed_adjusted_branch_update_after_error_in_drop/]]
 
+> [[fixed|done]] (I presume) --[[Joey]]
diff --git a/doc/bugs/__34__.git__47__HEAD__58___openFile__58___resource_busy__34___after_copy/comment_2_399dcbe7f3772526efbe13bd5b13156d._comment b/doc/bugs/__34__.git__47__HEAD__58___openFile__58___resource_busy__34___after_copy/comment_2_399dcbe7f3772526efbe13bd5b13156d._comment
new file mode 100644 (file)
index 0000000..f102bfa
--- /dev/null
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2023-04-04T18:13:49Z"
+ content="""
+Clearly a laziness bug, so the fix seems obvious and I've commited it.
+
+But I've not managed to reproduce it. It makes sense it would be
+intermittent. Please followup if you still see it after
+[[!commit 3eb51ee929c75376d004341f41aa38a1488558a3]]
+"""]]