<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/php-git.git/sapi/apache2handler, branch php-7.2.24</title>
<subtitle>git.php.net: repository/php-src.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/'/>
<entry>
<title>Sync leading and final newlines in source code files</title>
<updated>2018-10-14T10:54:08+00:00</updated>
<author>
<name>Peter Kokot</name>
<email>peterkokot@gmail.com</email>
</author>
<published>2018-10-14T10:54:08+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=60a69daec60f1886e166e8060556777819c66f98'/>
<id>60a69daec60f1886e166e8060556777819c66f98</id>
<content type='text'>
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-' &lt;newline&gt;'
characters plus a terminating '&lt;newline&gt;' 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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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-' &lt;newline&gt;'
characters plus a terminating '&lt;newline&gt;' 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
</pre>
</div>
</content>
</entry>
<entry>
<title>Trim trailing whitespace in source code files</title>
<updated>2018-10-13T12:14:50+00:00</updated>
<author>
<name>Peter Kokot</name>
<email>peterkokot@gmail.com</email>
</author>
<published>2018-10-13T12:14:50+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=902d39a3a79c6efe93c8879575fdd5a759cf03de'/>
<id>902d39a3a79c6efe93c8879575fdd5a759cf03de</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'PHP-7.1' into PHP-7.2</title>
<updated>2018-09-30T18:07:44+00:00</updated>
<author>
<name>Nikita Popov</name>
<email>nikita.ppv@gmail.com</email>
</author>
<published>2018-09-30T18:07:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=56d157851515178f8e27bd90b1ef4925d671fda6'/>
<id>56d157851515178f8e27bd90b1ef4925d671fda6</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed bug #75479</title>
<updated>2018-09-30T18:07:15+00:00</updated>
<author>
<name>Nikita Popov</name>
<email>nikita.ppv@gmail.com</email>
</author>
<published>2018-09-30T18:05:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=db80e0e2ad016cbff55cc6e1311b7ffe9ad7101e'/>
<id>db80e0e2ad016cbff55cc6e1311b7ffe9ad7101e</id>
<content type='text'>
Wrap the zend_signal_init() call, so the hook arguments line up.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Wrap the zend_signal_init() call, so the hook arguments line up.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'PHP-7.1' into PHP-7.2</title>
<updated>2018-09-09T19:29:29+00:00</updated>
<author>
<name>Stanislav Malyshev</name>
<email>stas@php.net</email>
</author>
<published>2018-09-09T19:29:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=788717d56d48f6697829d95cf9b9a49a35d53058'/>
<id>788717d56d48f6697829d95cf9b9a49a35d53058</id>
<content type='text'>
* PHP-7.1:
  Update NEWS
  Fix for bug #76582
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* PHP-7.1:
  Update NEWS
  Fix for bug #76582
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'PHP-7.0' into PHP-7.1</title>
<updated>2018-09-09T19:29:23+00:00</updated>
<author>
<name>Stanislav Malyshev</name>
<email>stas@php.net</email>
</author>
<published>2018-09-09T19:29:23+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=6623f3caca75398c930d0cece25eeff0efe95a7e'/>
<id>6623f3caca75398c930d0cece25eeff0efe95a7e</id>
<content type='text'>
* PHP-7.0:
  Update NEWS
  Fix for bug #76582
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* PHP-7.0:
  Update NEWS
  Fix for bug #76582
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'PHP-5.6' into PHP-7.0</title>
<updated>2018-09-09T19:27:44+00:00</updated>
<author>
<name>Stanislav Malyshev</name>
<email>stas@php.net</email>
</author>
<published>2018-09-09T19:27:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=024f3ac160228c9a7ace342b757cbd07934fa189'/>
<id>024f3ac160228c9a7ace342b757cbd07934fa189</id>
<content type='text'>
* PHP-5.6:
  Update NEWS
  Fix for bug #76582
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* PHP-5.6:
  Update NEWS
  Fix for bug #76582
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix for bug #76582</title>
<updated>2018-09-09T18:45:14+00:00</updated>
<author>
<name>Stanislav Malyshev</name>
<email>stas@php.net</email>
</author>
<published>2018-07-29T05:16:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=23b057742e3cf199612fa8050ae86cae675e214e'/>
<id>23b057742e3cf199612fa8050ae86cae675e214e</id>
<content type='text'>
The brigade seems to end up in a messed up state if something fails
in shutdown, so we clean it up.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The brigade seems to end up in a messed up state if something fails
in shutdown, so we clean it up.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix race conditions with Apache vhost vs. per dir config</title>
<updated>2018-02-01T14:24:31+00:00</updated>
<author>
<name>Anatol Belski</name>
<email>ab@php.net</email>
</author>
<published>2018-01-31T19:15:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=bced074124f65653071ccf29e0878ef725b09a49'/>
<id>bced074124f65653071ccf29e0878ef725b09a49</id>
<content type='text'>
If the same php_value/php_flag is present in httpd.conf and .htaccess,
the key is potentially shared between threads. Unfortunately we can't
intern these keys using the current mechanism, because the MPM is setup
before the SAPI module setup is even started. A more elegant way were
to implement a kind of string pool for the thread safe Apache SAPI
config directives with the mechanism similar to what is done for the
SAPI setup now, but doing a separate management.

(cherry picked from commit 73eb5a78b9caa18d35624765f9b972c1ba48855d)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If the same php_value/php_flag is present in httpd.conf and .htaccess,
the key is potentially shared between threads. Unfortunately we can't
intern these keys using the current mechanism, because the MPM is setup
before the SAPI module setup is even started. A more elegant way were
to implement a kind of string pool for the thread safe Apache SAPI
config directives with the mechanism similar to what is done for the
SAPI setup now, but doing a separate management.

(cherry picked from commit 73eb5a78b9caa18d35624765f9b972c1ba48855d)
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix race conditions with Apache vhost vs. per dir config</title>
<updated>2018-01-31T19:15:30+00:00</updated>
<author>
<name>Anatol Belski</name>
<email>ab@php.net</email>
</author>
<published>2018-01-31T19:15:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=73eb5a78b9caa18d35624765f9b972c1ba48855d'/>
<id>73eb5a78b9caa18d35624765f9b972c1ba48855d</id>
<content type='text'>
If the same php_value/php_flag is present in httpd.conf and .htaccess,
the key is potentially shared between threads. Unfortunately we can't
intern these keys using the current mechanism, because the MPM is setup
before the SAPI module setup is even started. A more elegant way were
to implement a kind of string pool for the thread safe Apache SAPI
config directives with the mechanism similar to what is done for the
SAPI setup now, but doing a separate management.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If the same php_value/php_flag is present in httpd.conf and .htaccess,
the key is potentially shared between threads. Unfortunately we can't
intern these keys using the current mechanism, because the MPM is setup
before the SAPI module setup is even started. A more elegant way were
to implement a kind of string pool for the thread safe Apache SAPI
config directives with the mechanism similar to what is done for the
SAPI setup now, but doing a separate management.
</pre>
</div>
</content>
</entry>
</feed>
