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

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

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-02-01 18:54:01 CET

-----Original Message-----
From: Jochen Wendebaum [mailto:jochen@wendebaum.de]

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

It would take less work overall to do the manual merge, load it into Svn,
and then have everyone check out a new working copy. But that's a big-bank
approach, which assumes you can take a few day's hit right now.

If you *needed* to be able to introduce Svn incrementally, you could start
by installing each person's code onto a separate branch of the project(s).
Then as each developer is brought into a fully shared Svn system, you merge
his code into the main, and he starts using a WC based on main. Requires
more bookkeeping, but it wouldn't take very long to import a developer's
code base into a branch and check him out a WC of it.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 1 18:57:18 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.