Richard Riley wrote:
Its really simple.
Use git.
And stick two fingers up at the windows developer base ;)
It works, is fast and is rapidly becoming the industry standard. Do not
sue something for "moral grounds" like the awful bzr used for emacs.
Mercurial is just as popular, especially if you want to support windows projects
in parallel with Linux ones ...
TortoiseHg just works on both windows and Linux, integrates nicely into file
managment and plays nicely in Eclipse ... TortoiseGit is windows only and has
compatibility problems.
Its designed as a fast, efficient DVCS.
Ditto ...
But it does not matter two hoots which one you go for ...
http://lsces.co.uk/hg/
we can quite happily use either locally. All that needs to be agreed on is HOW a
master distribution clone is managed. Managing transfers of patches between
sites requires a lot more management which SVN simply provides by default.
Keeping the 'master' as SVN may not be such a bad thing as long as git/hg
mirrors also exist.
I've been through many hoops over the last year since git was forced on me by
other projects ... git needs to start playing better with windows users, as it's
current offering does NOT work on sites where other SSH activities are already
installed. WHile hg just worked out of the box.
The current problem is that neither play well together in the area of sub-repos
and this is an area that is still very much work in progress? Manually cloning
each individual element does currently work though, and that is how I'm
currently remaining sane ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
