See inline. Kiall
Sent from a mobile - sorry for being short! On Aug 27, 2011 5:22 p.m., "Lester Caine" <les...@lsces.co.uk> wrote: > > 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! > "Supported by tools in eclipse" - to the vast majority of people, this is useless. I would bet no single IDE / text editor has over 10% share of those involved with PHP. Choosing your SCM based on a single IDE 'doing it all' is not a smart move! Ever. > 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. > To be honest, this (to me) sounds like you're chasing a dream of one tool to rule them all. You're negative against TortoiseHg is that it doesn't do SVN nicely?!?! What's wrong with using the right tool for the job? Native CLI, or one of the GUIs.. eg TortoiseHg for HG, TortoiseGit for Git and TortoiseSVN for SVN. > The Git GUI support is considerably more disjointed. Nothing is available that works transparently cross platform! The EGit plugin for Eclipse still does not 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. > I'm betting you could have been back to the same, or higher, productivity levels a long time ago -- if you hadn't been fighting to make the new DVCS look at feel like your old VCS ;) Anyway - Re GUIs I've only ever used TortoiseGit, and even than only when I'm doing windows dev, but it works perfectly. Submodules included. (That is - unless you try and use it to connect to Hg or TFS or well... anything other than git!). And ignoring the current state of play - the GUIs will continue to mature over time. > 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 ;) If Hg was as significantly better than git as you've been portraying, surely people would be jumping by the thousand onto the Hg bandwagon?
