docs(okf): add the six missing carried-patch rows, refresh seven stale upstream statuses - #563
Merged
Merged
Conversation
…s stale The reference stopped at 0012 while Scripts/patches/ has run to 0018, so the four thread-safety patches from the #344 to #374 chain, the #484 null-context guard and the new #555 GCPnts fix were all missing from the ecosystem-level view of what we carry. Adds 0013 to 0018, and refreshes every upstream status against the GitHub API rather than from the previous note: OCCT#1323, #1331, #1374, #1377, #1380, #1382 and #1318 have all merged since this file was written. The two still shown as open, #1386 and #1388, were re-checked and are accurate. 0018 is our first fix filed as a PR with no companion reproducer issue, which is the practice maintainer dpasukhi asked for on OCCT#1409: "In case if you preparing PR, no needs to create Issue. Issue is recommended to create when you are not working on PR" The policy already records that rule, added on 2026-07-30. This only reconciles the table's intro with it, since the table now has a row on each side of the change. Refs #555 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PR-only rule is already in the policy, added on 2026-07-30 with dpasukhi's quote and link. What was missing is everything downstream of it.
What this fixes
okf/references/carried-occt-patches.mdstopped at0012whileScripts/patches/has run to0018. Six patches were absent from the ecosystem-level view of what we carry and why:0013ShapeUpgrade_UnifySameDomainnull-pcurve dereference (#348)0014CDF_Applicationcached-driver reentrancy (#349)0015CDM_Application::myMetaDataLookUpTable(#353)0016Resource_Manager::Debug+Storage_Schemacurrent data (#374, redesigned per #518)0017ShapeFix_ComposeShell/ShapeUpgrade_WireDividenull context (#484)0018GCPntspoint counts (#555)Seven upstream statuses were also stale. Re-checked every referenced item against the GitHub API rather than trusting the previous note, and OCCT#1323, #1331, #1374, #1377, #1380, #1382 and #1318 have all merged since the file was written. The two still listed as open, #1386 and #1388, were re-checked and are accurate. #1374 is merged but not yet in a release, so the
0003retire-when footnote now says that rather than implying we are waiting on review.The rule the table now straddles
0018is the first fix we have filed as a PR with no companion reproducer issue, which is what maintainer dpasukhi asked for on OCCT#1409:Rows
0001to0017still show the older repro-issue-then-fix-PR pairs. Those stay as the accurate historical record rather than being retitled after the fact; the intro now says which side of the change each row is on, instead of claiming the whole table predates it.Why this is separate from #519
#519 is the kernel rebuild and the three patches riding it, targeting
refactor/381-pass1b. This is a reference doc with no bearing on that binary, so it goes tomainon its own and does not wait on Pass 1b landing.0018's own filing note stays in #519 where the patch lives.Docs only, no code paths touched.
Refs #555
🤖 Generated with Claude Code