diff --git a/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir.mdwn b/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir.mdwn
index 77fb4e4885..31648dc593 100644
--- a/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir.mdwn
+++ b/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir.mdwn
@@ -25,6 +25,8 @@ configs.
 Is it at all common to set `git config fetch.fsckObjects true` or 
 `git config receive.fsckObjects` true?
 
+> [[fixed|done]] in git --[[Joey]] 
+
 ----
 
 There is also potential breakage from git fsck now warning about symlink
diff --git a/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir/comment_4_3da394c6155827fb6d9e64f1fdc214a1._comment b/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir/comment_4_3da394c6155827fb6d9e64f1fdc214a1._comment
new file mode 100644
index 0000000000..97b6c04816
--- /dev/null
+++ b/doc/todo/deal_with_git_fsck_symlinkPointsToGitDir/comment_4_3da394c6155827fb6d9e64f1fdc214a1._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2024-06-04T10:35:09Z"
+ content="""
+Fixed git was released. All these versions fix it: v2.45.2 v2.39.5, v2.40.3, v2.41.2, v2.42.3, v2.43.5, and v2.44.2
+
+That does leave the fsck.symlinkTargetLength as potentially still a problem
+on Windows, but I think I'll consider this closed and if that does actually
+lead to problems on windws we can revisit.
+"""]]