Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50511 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1900 invoked from network); 25 Nov 2010 09:49:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2010 09:49:08 -0000 X-Host-Fingerprint: 93.97.160.27 93-97-160-27.zone5.bethere.co.uk Received: from [93.97.160.27] ([93.97.160.27:7265] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/53-20008-2113EEC4 for ; Thu, 25 Nov 2010 04:49:07 -0500 Message-ID: <9A.53.20008.2113EEC4@pb1.pair.com> To: internals@lists.php.net Date: Thu, 25 Nov 2010 09:49:03 +0000 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 References: <4CEE0ADA.5010705@lsces.co.uk> <4CEE1327.7050405@lsces.co.uk> In-Reply-To: <4CEE1327.7050405@lsces.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 93.97.160.27 Subject: Re: [PHP-DEV] git anyone? From: php@nickpope.me.uk (Nick Pope) On 25/11/10 07:41, Lester Caine wrote: > Patrick ALLAERT wrote: >> 2010/11/25 Lester Caine: >>> Have you used git on Windows Pierre ... It is a joke! >>> Yes one can get it to work, but only if you do not use anything that >>> the git >>> cygwin install destroys! And as yet there is no consensus on getting it >>> working cross platform in things like Eclipse. >>> >>> At least hg works out of the box on both linux and windows, but like git >>> THAT does not properly support sub-repo's and makes managing nice >>> modularly >>> constructed projects like PHP almost impossible. >>> >>> Trying to work with projects that write modular PHP code in either >>> git or hg >>> is simply not currently practical ... especially when half of your >>> user base >>> is still tied to windows! >> >> Git on Windows problems belong to the past since a while now: >> * mSysGit > Provide you don't use cygwin ALREADY on your machine !!! > Install mSysGit and existing packages stop working ... While I don't use Windows, I do know that msysgit keeps things separate and shouldn't clobber your cygwin setup. Perhaps you have an issue with your path? The state of Git on Windows is, yes, far from perfect, but certainly improving. A quick search yields up some nice looking tools for Git on Windows: http://www.makeuseof.com/tag/5-windows-git-clients-git-job/ SmartGit looks pretty good (non-commercial use). Git on Windows is not 100% friendly, but is workable. We have people using it everyday at work here. >> * TortoiseGit > TortoiseHg does it RIGHT and works on both Linux and Windows. > TortoiseGit does not work on Linux ... I use Linux and quite frankly I couldn't give a damn about things like Tortoise*. Such tools are nice enough for Windows where command prompt is so desperately useless, but they are no substitute for a real understanding of the command line interface of the SCM tool. I have a decent "command prompt" in Linux and it is a hell of a lot quicker (and, I would say, easier) to use. In short - I'm not sure why you're trying to slag off Git because TortoiseGit is no good for Linux. What is wrong with git-gui, gitk or gitg? > Personally I run hg since I need cross platform capability for my > customers, and hggit quite happily links to github but all of this has > to be managed outside Eclipse since none of those tools work reliably. > > And we STILL have the problem of handling modular projects since neither > do 'sub-repo' reliably. This area seems to be in a similar state of > chaos to PHP with different factions all pushing their own agendas. Both > git and hg are targeting compiled applications and ignore handing > scripted applications like php, python, ruby and the like. 'You fix the > problems when you build a project' simply does not work when you do not > have anything to build! So while it may work for building PHP as a > single program, a packaged distribution is a different matter. Ultimately I'm a +1 for Git. The proper branching/merging would solve so many issues that have been addressed recently on the mailing list regarding the pollution of trunk with incomplete and broken features, as well as BC breakage by feature removal...