Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60875 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13291 invoked from network); 18 Jun 2012 02:32:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jun 2012 02:32:02 -0000 Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vb0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:50674] helo=mail-vb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/EA-49496-F139EDF4 for ; Sun, 17 Jun 2012 22:31:59 -0400 Received: by vbbfs19 with SMTP id fs19so3074534vbb.29 for ; Sun, 17 Jun 2012 19:31:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=o4jZucxVZt3VXec84ukJGd3RuhCDrZpTIO5HamqFa2E=; b=K/MkM8Q7NvDQQCY6x04jssZ/kpnU493cMeRxhVyj4/CW+0+F651/iSj8KEz2cg/sSU oYfXLnJlqvIPd9iMw8AdxmB52s5Wu6eOkDlBCTPzeiiWTT7uK5HitOtTecuJjbpW9Wvo E0lvWvQA7s5IYvHjuXPbOF8fL2fKB2SY3AlEbdW+/UmHt11lsE1Iogjs95KsImGDrVNI 0Pq4sO6ZoZE4hGC56Nx2N1uV8UEnR2oATZFUaCMP2R+FUk5DmuPHrRcFIjC119kDrUr2 hzubaYW/UfBQ6YqPwiUYbfrUgTLe42JGL9/QpKQSts2MAiXZgruRLD8WTWEAsSk66ByT JyQw== Received: by 10.52.155.193 with SMTP id vy1mr5593647vdb.123.1339986716322; Sun, 17 Jun 2012 19:31:56 -0700 (PDT) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.220.162.141 with HTTP; Sun, 17 Jun 2012 19:31:36 -0700 (PDT) In-Reply-To: <1339929930.2295.0.camel@guybrush> References: <1339929930.2295.0.camel@guybrush> Date: Mon, 18 Jun 2012 10:31:36 +0800 X-Google-Sender-Auth: vIkFpMfA307xe9uytXy6Ggy7ayo Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: Stanislav Malyshev , Dmitry Stogov , PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] what is the rule of merging fix to release branch? From: laruence@php.net (Laruence) On Sun, Jun 17, 2012 at 6:45 PM, Johannes Schl=C3=BCter wrote: > On Sun, 2012-06-17 at 13:20 +0800, Laruence wrote: >> Hi: >> =C2=A0 =C2=A0 there comes some bug of a already fixed issue (PHP5.4.4) >> >> =C2=A0 =C2=A0 the fix(#61998) =C2=A0is here >> https://github.com/php/php-src/commit/90e23107a2acba1fd53b7e799372eb9f24= 194a56 >> >> =C2=A0 =C2=A0 but seems this fix is not merged into 5.4.4 when it was re= leased? >> >> =C2=A0 =C2=A0 so, what is the rule? =C2=A0:) > > See also http://news.php.net/php.internals/59485 > > johannes thanks , sorry for missed that ;) thanks > > --=20 Laruence =C2=A0Xinchen Hui http://www.laruence.com/