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

Introducing SVN, best practices for people that work together without any version control

From: Jochen Wendebaum <jochen_at_wendebaum.de>
Date: 2005-02-01 08:25:50 CET

Hi all,

we are introducing subversion in our development department (30ppl). Most
of us have single projects and work alone which makes the introduction
quite easy (well, more and more collaborative work is coming so it's the
time now to get a system into the department). Some of the people work
together already on a single project and share the sourcecode (by copying
it!), everyone works on his files and every 6 weeks they do a manual merge
(which takes half a day). So now we are in the situation that such a merge
would have to take place, and at the same time we start with subversion.

My question is how to go on...

1. first do the manual merge and then introduce svn
2. install svn, do the merge with svn

If we do the merge with svn, how shall we proceed? Put both version into
the db, or only one, and then merge them on a local copy?

I am a bit clueless atm...


Jochen Wendebaum

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 1 17:29:37 2005

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.