Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50789 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17299 invoked from network); 1 Dec 2010 15:16:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Dec 2010 15:16:20 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 unknown Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:46744] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D5/45-25725-8B666FC4 for ; Wed, 01 Dec 2010 10:16:09 -0500 Received: from [192.168.1.31] (ppp-93-104-47-176.dynamic.mnet-online.de [93.104.47.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id C30DD4B6A4; Wed, 1 Dec 2010 16:16:05 +0100 (CET) To: David Soria Parra Cc: internals@lists.php.net In-Reply-To: References: <4CEE0ADA.5010705@lsces.co.uk> <4CEE1327.7050405@lsces.co.uk> <9A.53.20008.2113EEC4@pb1.pair.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 01 Dec 2010 16:16:04 +0100 Message-ID: <1291216564.27624.43.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] git anyone? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Wed, 2010-12-01 at 10:01 -0500, David Soria Parra wrote: > On 2010-12-01, Pierre Joye wrote: > > hi, > > > > I think we have enough feedback about this topic. We will come back > > with a detailed proposal explaining how it could be done, which tools, > > etc. > > I think it would be good to have people willing to help out with evaluating > certain DVCS. In particular we need someone for BZR to put together a good > RFC. I'll probably help evaluating Git and Mercurial. > An evaluation requires a clear set of goals first. Like: Why change? What is broken? What can be improved? What are existing requirements? Once that is done one can start evaluating specific tools. johannes