[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Good strategies for incorporating an external code drop

From: James French <James.French_at_naturalmotion.com>
Date: Wed, 9 Nov 2011 14:33:05 +0000

-----Original Message-----
From: KARR, DAVID [mailto:dk068x_at_att.com]
Sent: 08 November 2011 20:31
To: users_at_subversion.apache.org
Subject: Good strategies for incorporating an external code drop

Subversion works fine when developers have access to the SVN repo. I'm working on a project where one of the developers for one of the projects doesn't have access to our network. When he makes changes he sends me a zip file with the new contents of the project.

When I incorporate his changes, I've been going through a somewhat manual process, doing a "diff -cr" between the old and new, copying in files that have changes, copying in new files with "Only in <new>" and deleting files with "Only in <old>".

Is there an easier way to do this?

I'd try and change it so he does have access, restricted to just subversion if that's the issue. Then you can use permissions to lock him down to a specific dev branch. Much easier.
Received on 2011-11-09 15:33:41 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.