On Thu, Sep 23, 2004 at 01:00:13PM +0100, Andrew Savory wrote:
Hi,
On 23 Sep 2004, at 12:52, Matt Parker wrote:
I have, however, read the docs on Subversion and it hasn't interested me enough to even want to change, at least for my own work. I can't see the "killer reason" for changing.
Neither did I.
But then I was forced to try it on a major publisher's development project, and since then it's been a question of "how soon can I migrate our own repositories" rather than "should we convert our own repositories".
If you work with a local CVS repository, the need is admittedly less urgent - but that's comparatively rare. Wherever you have two or more people collaborating with a server-based repository, SVN makes a -lot- of sense. And finally, control over directories! Seamless branching! Web integration for free! Webdav access to the repo! Non-login accounts! HTTP tunnelling!
It's all good. Try it, you might like it. What's the worst that can happen[1]? :-)
A.
[1] ... you find out your preferred tool doesn't have SVN integration. Time to kick the vendor / developer and tell them to get with the program, whilst brushing up on your 'leet command-line skills.
JOOI, what tool do you use for development? (I still use the tools that I've been using for a few years now, vim and command line repository tools)
Thanks,