RE: Pair Programming with Subversion

I do a defacto variant of your 'Pair Programming'. I collaborate with my partner using a range of always-on tools including text and voice chat, and we run subversion using svnserve over a VPN.
 
In our present phase we both have our own working copies of the same development branch. We can separately make commits, and we can immediately update our own versions with the other's changes using the built-in merge capabilities of SVN (update). This is working extremely well and I believe it would avoid any permission problems (since you own your own working copy). It is also very little hassle, because you don't need to worry about hand-merging changes from one branch back and forth -- it all just works (except for the occasional conflict, which needs handling anyway).
 
Glenn.

-----Original Message-----
From: andy.glew@amd.com [mailto:andy.glew@amd.com]
Sent: Thursday, 1 April 2004 04:38
To: bmathis@directedge.com
Cc: users@subversion.tigris.org
Subject: RE: Pair Programming with Subversion

> As bad as it is, why not create another user account that both of you log in to when you're developing?
 
I work at a big company (AMD), where we do not have the ability to
create accounts. IT won't do it.
 
 
Received on Thu Apr 1 06:57:55 2004