UnsnoopAutoPacket does not need to be recursive #640
Merged
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
codemercenary
force-pushed
the
fix-unsnooppacket
branch
from
ce9dedd to
228d1ac
Compare
Context-recursive packet processing has been deprecated for several major versions, there is no need to recursively create packet factories to the root when unsnooping.
codemercenary
force-pushed
the
fix-unsnooppacket
branch
from
228d1ac to
841e33e
Compare
codemercenary
added a commit
that referenced
this pull request
Jul 11, 2015
UnsnoopAutoPacket does not need to be recursive
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.
Context-recursive packet processing has been deprecated for several major versions, there is no need to recursively create packet factories to the root when unsnooping.