Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74271 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 324 invoked from network); 17 May 2014 11:13:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 May 2014 11:13:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.220.178 cause and error) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.220.178 mail-vc0-f178.google.com Received: from [209.85.220.178] ([209.85.220.178:45924] helo=mail-vc0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/36-35141-B4447735 for ; Sat, 17 May 2014 07:13:15 -0400 Received: by mail-vc0-f178.google.com with SMTP id hq16so7634560vcb.9 for ; Sat, 17 May 2014 04:13:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:from:mime-version:in-reply-to:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=r1x9gIyzlNpRDkZZEVSlvaCwpetzjb6mIctkrnYD09g=; b=Y81Djeu/NBUXYI07ASFjMzEu8IVG3sOTUe8I70aOhgnEqQoclLAtyjqCYFtxioJqBJ JBVxCtAhnDEzl5O8chgEV/dZnbDyg+gBfvSUqIcNKTk2B3w5BNp56yJoGh+dLlN29gMK MN7aE2VpdLPZX6q/lyj5m46FkpybI7F/juXAu5VbN920q4eJllIGp6L8lrSghO74VlBf r0GmQ4jJom2brpucZBufuHzs9AyGzDiQw7f98uw+9gjrP5qOGQLUG/Indk/iqMwBGYGV lHXLMKWURs333XAdNORfj63EJxOZ5ZFtCgxs9dRAxi/BS6fglT8ynDhMKt0sgj5iX474 mJeA== X-Gm-Message-State: ALoCoQmoAGieJAlzMfIVsQJb3hEq+MvZi8lIF4IgxWKSucwz0SWH5zGBxzIjWoNMdbhW0Uw4g1ODxCIQC8H430v0TMNHMMpv3R5ufU/FrLklk4P1Z7ox7svpnibirvtyfJZImHHwuayE X-Received: by 10.52.37.135 with SMTP id y7mr1799545vdj.38.1400325192858; Sat, 17 May 2014 04:13:12 -0700 (PDT) References: <3939936079205827190@unknownmsgid> <2602f5303ca0c63345ec2d234ab24003.squirrel@webmail.klapt.com> Mime-Version: 1.0 (1.0) In-Reply-To: <2602f5303ca0c63345ec2d234ab24003.squirrel@webmail.klapt.com> Date: Sat, 17 May 2014 14:13:09 +0300 Message-ID: <-4728021288282848432@unknownmsgid> To: Anatol Belski Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] A call for help (urgent) From: zeev@zend.com (Zeev Suraski) No, you're watching the Voting RFC going haywire. It's the second time we have an RFC that deals with internal implementation as opposed to features and functions, something the RFC process was never designed to do. And it appears to be failing, much like it almost failed the last time around. Last time it happened I raised the hope that non-engine contributors will refrain from placing votes on such RFCs, we may need to (try and) formalize it. Zeev > On 17 =D7=91=D7=9E=D7=90=D7=99 2014, at 14:02, Anatol Belski wrote: > >> On Sat, May 17, 2014 12:53, Zeev Suraski wrote: >> All, >> >> >> In case there's any chance people lost track in the noise: >> >> >> Please, please - vote No on >> https://wiki.php.net/rfc/size_t_and_int64_next#vote >> >> >> We're in an unprecedented situation where almost all of the code >> contributors to the engine are against a patch that is being forced on t= hem >> for no reason, negates months of hard work performed to get us phpng, an= d >> is somehow enjoying a majority (almost exclusively from people who are n= ot >> engine contributors). >> >> I urge everyone with a right to vote (and only those, as per >> https://wiki.php.net/rfc/voting) to vote no, and even those who voted >> yes to revert their votes to no. >> >> We need your help! > Am i watching a CNN movie? > > Cheers > > Anatol >