comment
authorJoey Hess <joeyh@joeyh.name>
Mon, 5 May 2025 17:41:45 +0000 (13:41 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 5 May 2025 17:41:45 +0000 (13:41 -0400)
doc/bugs/OsPath_bld_of_g-a_shows_files_needlessly_modified/comment_1_fe5020608317e23c95eb9ac2ed0d689d._comment [new file with mode: 0644]

diff --git a/doc/bugs/OsPath_bld_of_g-a_shows_files_needlessly_modified/comment_1_fe5020608317e23c95eb9ac2ed0d689d._comment b/doc/bugs/OsPath_bld_of_g-a_shows_files_needlessly_modified/comment_1_fe5020608317e23c95eb9ac2ed0d689d._comment
new file mode 100644 (file)
index 0000000..9e6ebd4
--- /dev/null
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2025-05-05T17:34:53Z"
+ content="""
+Does your test case reproduce the problem reliably, or only sometimes?
+
+Typically when git gets into this state it's an intermittent problem based
+on timing. I want to make sure the OsPath build flag is not a red herring
+before pursuing that.
+"""]]