Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54628 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89823 invoked from network); 15 Aug 2011 20:33:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Aug 2011 20:33:22 -0000 X-Host-Fingerprint: 134.29.239.140 140-239-29-134.minnesota.edu Received: from [134.29.239.140] ([134.29.239.140:6234] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F8/00-21941-192894E4 for ; Mon, 15 Aug 2011 16:33:21 -0400 Message-ID: To: internals@lists.php.net Date: Mon, 15 Aug 2011 15:33:13 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 References: <4E3F02E8.2050402@sugarcrm.com> <4E450EB1.6090502@lsces.co.uk> <4E456F2F.7030809@sugarcrm.com> <4E45755F.3020005@lsces.co.uk> <4E4578B6.6050708@sugarcrm.com> <4E45A2BD.7060506@lsces.co.uk> <4E45AFDF.9000001@sugarcrm.com> <4E45B6A9.9080607@lsces.co.uk> <4E46F26E.1000607@garfieldtech.com> <4E4784E7.9050700@lsces.co.uk> <4E48331F.1080403@lsces.co.uk> In-Reply-To: <4E48331F.1080403@lsces.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 134.29.239.140 Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control systemfor PHP (or not). Call for Participation. From: justin.rovang@minnesota.edu (Justin Rovang) On 8/14/2011 3:42 PM, Lester Caine wrote: > Gwynne Raskind wrote: >>> The only real disadvantage to hg is having to handle python code to >>> maintain >>> > it, people might start converting from PHP;) Although phphgadmin is >>> a start >>> > to improving the php interface support and could be a good start at >>> a fully >>> > PHP managed interface to a PHP repo? >> I'm starting to think we should take a cue from Linus and just do as >> we did with bugsweb, newsweb, and so forth: Build our own >> (Hg/Git-compatible) DVCS from scratch! >> >> (I'm joking... mostly.) > It's not such a silly idea ... In reality both git and hg get modified > to provide custom facilities, so creating at least a clean php based > front end to a DVCS engine makes perfect sense. Especially if it links > in with bugsweb and perhaps highlights hotfix or other patch information > directly in the code base? Commits tag the relevant bug report > automatically? And patch accepts both hg and git inputs for those > without karma, or would commit for those with? > > I have been more than happy with hg working into git repos I did simply > assume that there would be an extension for git to handle hg in the same > way, but it would appear not? As far as I can tell from the hggit > extension, mirroring the git information is not particularly difficult, > so a 'hybrid' that could provide both hg.php.net and git.php.net views > seems practical, and commits need to be managed via karma, so processing > that should not be difficult? But the problem area I still see is the > handling of submodule/subrepo commits where they cross several > submodules ... that was an area where custom scripts used to exist for a > couple of the projects I work with and I think THIS may be an area where > a scratch built interface may be a possible option. > If one is made from scratch, I propose calling it "Phit"! Submodule support in both still leaves something to be desired. Instead of divergence, a large project like PHP could swing enough influence and developer base to benefit development for one or both of the DVCS's. (Probably a pipe dream :o )