Skip to content

Conversation

DarkFire01
Copy link

As promised in our last meeting here's a blog post about some of the findings i have found from WDDM and the consequences of just jumping into it too fast.

@reactos-buildbot
Copy link
Collaborator

Thanks for your contribution!
I have built and deployed your changes to https://pr135.web-content.reactos.org and will also do that for your future changes.

Copy link
Member

@learn-more learn-more left a comment

Choose a reason for hiding this comment

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

Overall it reads very nice.
I added some nitpicks, and some general comments for improvements.
Considering it is a fairly technical blog post, I added an elaboration for one abbreviation, maybe some more would be needed?

Copy link
Contributor

@cbialorucki cbialorucki left a comment

Choose a reason for hiding this comment

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

I will probably need to give this a second pass before approving, but these changes will give you a better base I think :) Feel free to take creative liberties with my suggestions.

@DarkFire01 DarkFire01 force-pushed the wddmlog branch 3 times, most recently from 6054417 to c0aaaac Compare October 7, 2025 22:18
@DarkFire01 DarkFire01 force-pushed the wddmlog branch 2 times, most recently from 7fe6bcc to e668e8e Compare October 11, 2025 17:31
Co-authored-by: Stanislav Motylkov <[email protected]>
Co-authored-by: Carl J. Bialorucki <[email protected]>
Co-authored-by: Mark Jansen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants