Fix MBusFrame type field name - #23
Open
Cougar wants to merge 1 commit into
Open
Conversation
Cougarforce-pushed
the
fix-MBusFrame-type-field-name
branch
from
October 27, 2018 14:07
65a7fcc to
efd1320CompareCougarforce-pushed
the
fix-MBusFrame-type-field-name
branch
from
October 27, 2018 14:38
efd1320 to
ddadfebComparephlundblom added a commit
to Sensenode/python-mbus
that referenced
this pull request
Mar 16, 2021
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 freeto 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.
This is fix for typo in mbus/MBusFrame.py where "stop" field was added twice