Repository navigation
[Sync-En] opcache, imagebmp: explain use_cwd and revalidate_path, document the bit depth of saved BMPs - #3876
Merged
Conversation
…ument the bit depth of saved BMPs
This file contains hidden or 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
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.
Translation of php/doc-en#6118 (commit 3feebd8c17): explains what opcache.use_cwd and opcache.revalidate_path do, in reference/opcache/ini.xml.
Translation of php/doc-en#6117 (commit 9dced3f1c0): documents the bit depth of the BMP saved by imagebmp(), with a new changelog row and a 1 bit example.
EN-Revision updated. Also dropped a few stale lines in passing: the PHP < 5.5.6 limit for opcache.max_accelerated_files, two TODO comments, and the outdated opcache.jit_buffer_size default (now 64M, as in EN).
Fixes: #3874
Fixes: #3875