Update QNameDictionaryTextRecord encoding to Protocol Version V8.0 - 2019/03/13 #16
Conversation
This file contains 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
|
following an email sent to microsoft, they have modified the documentation: 02/07/2023 https://learn.microsoft.com/en-us/openspecs/windows_protocols/mc-nbfx/94ebe168-ee0d-4939-a703-01c9784eb843 |
|
Thanks a lot for the PR and work on this. Unfortunately I don't have any permissions on this repository anymore (so can't merge it). Maybe @takeshixx still does? Otherwise it might be worth forking it. I don't work on this area anymore, so unfortunately can't reasonably maintain it. |
|
Nope, I'm not part of the org anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After debugging the lib for @sfonteneau issue #15 I found out the QNameDictionaryTextRecord encoding has changed in V8.0
(even if microsoft doc is not updated)