Jucs ipv6 rebase #6
Closed
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
|
Thanks. Yes, it might be useful to look at. Supporting Linux only isn't an option though. |
|
IPv6 is (mostly) supported now. |
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.
The repo git://github.com/jucs/iodine.git started with a version of iodine from a few years ago, and added IPv6 support. I'm not sure if these changes are useful, but in order to have a proper look at them I rebased them on top of the commit in yarrick/iodine from which they actually started, with some keywork expansions squashed and some generated files clipped. The result is the branch jucs-ipv6-rebase in my repo, see above.
It cannot be merged automatically onto the current development tip (there are conflicts and such) but I thought it might be useful to have this information present when adding full IPv6 support.