Skip to content

Conversation

pietroalbini
Copy link
Contributor

This PR expands the documentation about known problems to clarify how to access the database and the ways to know about new KPs being discovered.

@pietroalbini pietroalbini requested a review from skade January 23, 2025 14:13
Copy link
Contributor

@skade skade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given feedback in chat, I'm now happy with the formulation.

@pietroalbini
Copy link
Contributor Author

bors merge

@bors-ferrocene
Copy link
Contributor

Build succeeded:

@bors-ferrocene bors-ferrocene bot merged commit 5e98746 into main Jan 23, 2025
5 checks passed
@bors-ferrocene bors-ferrocene bot deleted the pa-known-problems branch January 23, 2025 16:03
Hoverbear pushed a commit that referenced this pull request Jan 23, 2025
ferrocene-automations bot pushed a commit that referenced this pull request Jan 24, 2025
bors-ferrocene bot added a commit that referenced this pull request Jan 24, 2025
1245: [1.83] Backport KP docs, release notes fix r=pietroalbini a=Hoverbear

Backports

* #1244 

Also backports rust-lang/rust@24906b5 which which upstream is also doing: rust-lang/rust#135934

In the case of 24906b5, this is somewhat of a special circumstance. We noticed during our own release process that our 1.81 (so 24.11) release notes had changed and this change (along with rust-lang/rust#126967 which was removed with rust-lang/rust#129995) had disappeared. We confirmed the fix for rust-lang/rust#129960 is indeed in tree, but upstream never ported the release note update to their main branch. This port is being done in rust-lang/rust#135934.



Co-authored-by: Pietro Albini <pietro.albini@ferrous-systems.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants