Group compatibilities per origin #807
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
|
I don't know what's happening with the Ubuntu builds. |
|
I was just thinking about this this morning. I think it might be better if we create a |
|
I have fixed the disk splitting issue, if you want to rebase on top of |
nmoinvaz
approved these changes
Oct 30, 2024
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.
As the documented purpose of zlib-ng is to be a drop-in replacement of zlib, and minizip-ng a drop-in replacement of minizip, I wanted to clarify which parts of mz_compat.h are for the original minizip compatibility (permanent compatibility), and which parts are for older minizip-ng compatibility (deprecated usage).
I've consulted the current headers at https://github.com/madler/zlib/tree/develop/contrib/minizip and I've grouped them accordingly.