Lester Caine <les...@lsces.co.uk> writes: > Richard Quadling wrote: >>> Having current SVN-only contributors learn it might going to be quite a >>> challenge. >> That's me. And I am VERY used to TortoiseSVN - a visual tool >> integrated into Windows Explorer (not IE, but the filesystem exploring >> tool for Windows). >> I really don't want to have to work at the command line. Sure I can, >> but the tool needs to be a LOT easier than that. > > I use CVS and SVN directly from Eclipse and I know exactly where you are > coming > from. Currently this all runs transparently on all platforms and many of the > reasons' given for wanting to change are already supported by additional tools > _in_ Eclipse. Up until recently DVCS systems did not have such will integrated > support, and this was the cause of most of my own problems. Having machines > running both Windows and Linux in parallel for testing purposes I certainly > don't want to be having to think which platform I am on and changing the help > manual!
Why would you need to change any manuals? You follow a procedure and the user decides which client he wishes to perform those procedures and to interface to the chosen vcs. > > TortoiseHg provides an independent integrated GUI which I currently use in > parallel with Eclipse to support Hg and git via hggit, but it lacks some of > the > nice features of the SVN integration. MercurialEclipse has made a lot of > progress in the last few months and is starting to mimic the SVN tools, but > still has a few rough edges. Certainly it's developers are targeted at making > that better. > > The Git GUI support is considerably more disjointed. Nothing is available that > works transparently cross platform! The EGit plugin for Eclipse still > does not gitk does for a start. or? > support submodules and is rather basic in it's other functions, but now that I > have my Eclipse/TortoiseHg setup working something like stably, I am actually > _almost_ back to the same functionality that I've had on CVS and SVN repo's > for > many years, and on the whole can just access github and gitorious via that. > > The jump to git by many projects had nothing to do with improving > functionality > and everything to do with jumping on 'this is the new sourceforge' > bandwagon. The majority of the world uses Windows - it does not mean it's the > right answer to the problem ;) The jump to git was nothing to do with a bandwagon. Its to do with the fact its fast, practical, well supported and efficient and supports distributed development as a core feature. To ignore it in favour of some klunky "established" system like the god awful svn would be to miss an opportunity to move to what has rapidly become the defacto vcs for many many people. Arguing that the "gui ui" is a little unwieldy is silly : it will improve and there are other utilities to handle it. git works better than any other vcs I have used : it is in active development and is gaining ground for a reason. As for working "transparently" cross platform .. How often do you move regularly between a windows machine and a linux mahine for desktop development? There are oodles of things that are not the same - one tiny issue with the *desktop* integration to git will not kill anyone - and besides, editors like emacs hide the OS anyway using something like the wonderful magit. The huge majority of development is done on your local branch anyway. I guess all I am saying is dont dismiss it because you think its too hard to use a slightly different GUI interface or that other people only adopted it because of vogue. People adopted it because it works and works efficiently and well. For those that really really dont know about git, listen to Linux himself:- http://www.youtube.com/watch?v=4XpnKHJAok8 and/or monitor the #git Freenode irc channel. Its popularity is nothing whatsoever to do with a bandwagon. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
