Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71204 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97657 invoked from network); 17 Jan 2014 09:21:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2014 09:21:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.123 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.123 smtp123.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.123] ([108.166.43.123:42367] helo=smtp123.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/30-29925-306F8D25 for ; Fri, 17 Jan 2014 04:21:07 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id E9E921A00C1; Fri, 17 Jan 2014 04:21:04 -0500 (EST) X-Virus-Scanned: OK Received: by smtp8.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 9E1E81A00C7; Fri, 17 Jan 2014 04:21:04 -0500 (EST) Message-ID: <52D8F5FF.6010007@sugarcrm.com> Date: Fri, 17 Jan 2014 01:21:03 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: =?UTF-8?B?T25kxZllaiBIb8WhZWs=?= , PHP Internals List References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [accepted] ldap_modify_batch From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > 2. Which version should ldap_modify_batch land in? Only in 5.6 or will > it be backported? Against which branch should I submit the pull > request or patch? (master? 5.5 (newest stable)? 5.3 (oldest supported > stable)? earliest possible?) Looking at the patch, I don't see a problem having it in 5.4 and 5.5. 5.3 is security fixes only, so it can't be there. And yes, best way to do it is to create a pull on github, let people review it and then have somebody merge it. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227