| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
* PHP-7.3:
Update SDK version for AppVeyor
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.2:
Update SDK version for AppVeyor
|
| | | |
|
| | |
| | |
| | |
| | | |
Change-Id: Ifff234133f4437bfe5c31c1f1e00092cd60e1d53
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Formerly, there was at most a single OPcache instance per user and the
so called system ID (which is determined from the PHP version).
Sometimes multiple OPcaches might be desired, though, particularly for
unrelated CLI scripts, which may even be necessary (e.g. for our test
suite in parallel mode).
We therefore introduce a new INI directive `opcache.cache_id` which
allows to configure independent OPcache instances for the same user.
We also use `GetUserNameW()` instead of `php_win32_get_username()`,
because the latter retrieves the user name encoded in the
`default_charset`, which can obviously yield different results for
different charsets, leading to OPcache "incompatibilities". Slightly
worse, some characters may not even be encodeable in the
`default_charset` and would be replaced by question marks, which could
result in different users sharing the same OPcache.
We also refactor, and re-use existing APIs to avoid duplicated code.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.3:
Update SDK version for AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.2:
Update SDK version for AppVeyor
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.3:
Use php-sdk-2.2.0beta5 on AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.2:
Use php-sdk-2.2.0beta5 on AppVeyor
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.3:
Update Appveyor CI to php-sdk-2.2.0beta4
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.2:
Update Appveyor CI to php-sdk-2.2.0beta4
|
| | | |
|
|/ /
| |
| |
| |
| | |
This is too unstable due to shared opcache state. Disabling it until
this issue is resolved to reduce the number of spurious failures.
|
|\ \
| |/
| |
| |
| | |
* PHP-7.2:
Replace broken binary SDK version
|
| | |
|
|\ \
| |/
| |
| |
| | |
* PHP-7.2:
Update SDK version for AppVeyor
|
| | |
|
|\ \
| |/
| |
| |
| | |
* PHP-7.2:
Update SDK version for AppVeyor
|
| | |
|
|\ \
| |/
| |
| |
| | |
* PHP-7.2:
Update binary SDK version for AppVeyor
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines.
According to POSIX, a line is a sequence of zero or more non-' <newline>'
characters plus a terminating '<newline>' character. [1] Files should
normally have at least one final newline character.
C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."
Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.
[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines.
According to POSIX, a line is a sequence of zero or more non-' <newline>'
characters plus a terminating '<newline>' character. [1] Files should
normally have at least one final newline character.
C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."
Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.
[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
|
| | |
|
|\ \
| |/
| |
| |
| | |
* PHP-7.2:
Update binary SDK version for AppVeyor
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.1:
Update binary SDK version for AppVeyor
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Update binary SDK version for AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.1:
Update binary SDK version for AppVeyor
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Update binary SDK version for AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.1:
Update binary SDK version for AppVeyor
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Update SDK version for AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.1:
Update SDK version for AppVeyor
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Don't ignore commits on NEWS, etc. on AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.1:
Don't ignore commits on NEWS, etc. on AppVeyor
|
| | |
| | |
| | |
| | |
| | | |
[ci skip] can be used explicitly, and otherwise it might ignore commits
with a code change.
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
* PHP-7.2:
Update SDK version for AppVeyor
bump versions
|
| |\ \
| | |/
| | |
| | |
| | |
| | | |
* PHP-7.1:
Update SDK version for AppVeyor
bump versions
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Update binary SDK version for AppVeyor
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.1:
Update binary SDK version for AppVeyor
|