Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103051 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35628 invoked from network); 7 Aug 2018 21:43:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Aug 2018 21:43:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.22 mout.gmx.net Received: from [212.227.17.22] ([212.227.17.22:58233] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BC/C1-18754-F621A6B5 for ; Tue, 07 Aug 2018 17:43:12 -0400 Received: from [192.168.2.102] ([87.167.201.185]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MhNk6-1fZSMY19oQ-00Mb6z for ; Tue, 07 Aug 2018 23:43:08 +0200 To: PHP internals Message-ID: <87f6edc8-a6a8-cf0e-5b48-4f407e652b79@gmx.de> Date: Tue, 7 Aug 2018 23:43:11 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:k79JycQ/K9u1RgCJovV5dATVwo0VKi5nPin945GR4/v9IK7Y1Qh ihy1clv7OoOnG1UHUYG/v/OORL+2S6lAEMDc/L4nnXakxqgk/C+IeVFnEVLvDlpF8eZXQqQ 1qdh4FflacTvCQN7iQymgCF7q7UJTGi0tVQIz70kGfSmKc1fWwVHC+PFpjjxeZWvTf1Z94w L9aRmv0reNjb+ndok5TzA== X-UI-Out-Filterresults: notjunk:1;V01:K0:RBkx4MkQ1lA=:ae8/9zZyYartKNz6Eas71j fZta5Cz4aSQLbCilcTNO3ZjJWQd9vbgxA53pQRpiNnwTRWMK40BfW7fK2+5nT2m2Ei4YTt9RU ckYKszUHv65X/KUMeMoR1x4sN5hLuAsibaZYc38tN30wwJU+9QVLQXdKNldOO9Wyc6CQvn6Bx upGSrVxQvY3nL7BtepBC3RHUUx+9EfVLwXsaFqDr5byugQj+tyPibzlaw+ssuT73379F0IcCr k10NMoLXrgvQcRL9LoyNWStJQgnpAejbXPq31pBePMU3DgwVb4PKlm1u0UPthduDWSY2DDm9Q Qx2DTMEdsmEL1qc5u/lQZE72Qv6fhlrsGFnz/GUHD0DpEJqhsYKGT9/bmhyrqx8fampVnQ5Ef d4VGaqjedAyNglrbl+712DbI+bo0sB9ROpjazLErzQK2cjF9Gl8C94wxJtd1T+L7eiw1nwrSP faGqlRAdo7wOSads4BqgxEKL2NlJdC6ToKeKGyaKSXCvarGiebteRSyMosIHZM5VGdELupSiB AdtXsj5rcim9VE4D+TG5xXyfbTbJ1RLNL/ell6y5/x4sh/H1UxaIo3l6R9agSxVDPBeCwcepF 4q+vAa5AYrTmWFPg2mncUgABWbE5LHTEz0hmhmN3vCffRl/CkM24b9wa8hNsvI3lMlWC4MsDk gGq8LFE8JTLfw9GbCwEjeiDQ9oA4PrTW6MrTu4yzSRvjo593cx2xWxc+GDNcCpqsFg+Tt2h+J ZaSsAb30KOXQKOqjaZ3Ss0f9eD01NeYXwV5F7jpgbWrBR+w+z2IViMJ0Ghb5RZNxBRUnSLP5d 3KpnCjr Subject: NEWS vs. UPGRADING From: cmbecker69@gmx.de ("Christoph M. Becker") Hi! Do we have clear rules which changes are supposed to be listed in NEWS, and which ones in UPGRADING? -- Christoph M. Becker