Reset the code base to use the current master state in vibe.d. #26
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
Instead of trying to use the new code base that evolved from the HTTP/2 implementation, the plan is to first separate the existing code out to the vibe-http package, where regular development can continue. This state will be tagged as 1.0.0. At the same time, a different branch will be used to integrate the HTTP/2 code, which will at some point lead to a new 2.0.0 version tag.
s-ludwig
force-pushed
the
reset_to_current_vibe_d
branch
from
bcbfd26
to
06c6edf
Compare
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.
Instead of trying to use the new code base that evolved from the HTTP/2 implementation, the plan is to first separate the existing code out to the vibe-http package, where regular development can continue. This state will be tagged as 1.0.0. At the same time, a different branch will be used to integrate the HTTP/2 code, which will at some point lead to a new 2.0.0 version tag.