Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96424 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7614 invoked from network); 18 Oct 2016 11:31:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Oct 2016 11:31:37 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@ohgaki.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@ohgaki.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ohgaki.net designates 180.42.98.130 as permitted sender) X-PHP-List-Original-Sender: yohgaki@ohgaki.net X-Host-Fingerprint: 180.42.98.130 ns1.es-i.jp Received: from [180.42.98.130] ([180.42.98.130:40553] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8D/CA-40890-61806085 for ; Tue, 18 Oct 2016 07:31:36 -0400 Received: (qmail 84689 invoked by uid 89); 18 Oct 2016 11:31:30 -0000 Received: from unknown (HELO mail-qk0-f182.google.com) (yohgaki@ohgaki.net@209.85.220.182) by 0 with ESMTPA; 18 Oct 2016 11:31:30 -0000 Received: by mail-qk0-f182.google.com with SMTP id f128so274159838qkb.1 for ; Tue, 18 Oct 2016 04:31:30 -0700 (PDT) X-Gm-Message-State: AA6/9Rk5/Lvb5dBcJMcg07FycrzPSG0vD6JKTo2gSWcv+nL586YuwTO8qH8+NsPbyfxngM71VZirFd4pELQ//g== X-Received: by 10.55.121.133 with SMTP id u127mr1938064qkc.233.1476790284625; Tue, 18 Oct 2016 04:31:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.84.168 with HTTP; Tue, 18 Oct 2016 04:30:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 Oct 2016 20:30:43 +0900 X-Gmail-Original-Message-ID: Message-ID: To: Joe Watkins Cc: Niklas Keller , Leigh , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Improve uniqid() uniqueness From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi Joe, On Tue, Oct 18, 2016 at 7:32 PM, Joe Watkins wrote: >> This change should go through the standard RFC process and should be >> targeted at 7.2+ (master) *only*. > >> Please check with the RMs before merging functionality changes into >> release >> branches. All functionality changes need consent and consensus. Bug fixes >> (that don't change functionality or break BC) do not. > > You were told very specifically that the kinds of changes you proposed here > require an RFC. This comment is for original proposal that _changes_ output format, isn't it? It simply switches entropy source which we already relied on. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net