This repository has been archived by the owner on Sep 20, 2022. It is now read-only.
sniffer: get connection type from string format #40
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
miri64
force-pushed
the
sniffer/enh/conn-type-from-context
branch
from
b834d8d to
6460e98
Compare
The KISS approach alternative to RIOT-OS#38 (also includes RIOT-OS#39, because...). Disadvantage: we loose backwards compatibility for this tool.
miri64
force-pushed
the
sniffer/enh/conn-type-from-context
branch
from
6460e98 to
22516be
Compare
|
Rebased |
chrysn
pushed a commit
to chrysn-pull-requests/RIOT
that referenced
this pull request
Sep 20, 2022
…nn-type-from-context sniffer: get connection type from string format
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 KISS approach alternative to #38 (also includes #39, because...).
Disadvantage: we loose backwards compatibility for this tool.
Depends on #37 and #39