Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59036 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47910 invoked from network); 19 Mar 2012 17:24:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Mar 2012 17:24:13 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.153 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.153 smtp153.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.153] ([207.97.245.153:42074] helo=smtp153.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 72/22-36598-CBB676F4 for ; Mon, 19 Mar 2012 12:24:13 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp35.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 4C0E92C86D7; Mon, 19 Mar 2012 13:24:10 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp35.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id BF8322C86E3; Mon, 19 Mar 2012 13:24:09 -0400 (EDT) Message-ID: <4F676BB9.2080107@sugarcrm.com> Date: Mon, 19 Mar 2012 10:24:09 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Simon Schick CC: David Soria Parra , "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] php-src is now on git From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I don't know if someone asked just that before: > Are there plans reducing this list? > Branches (at least to me) seems to be something like big features, > bugfixes or releases that are or could actively be developed in the > future. With git, cost of branches is near zero, so we don't need to be too aggressive, and git workflow usually involves branching a lot. Of course, not every branch has to live in the main php repo :) -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227