[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: Tom Mornini <tmornini_at_infomania.com>
Date: 2005-02-01 19:14:07 CET

Hash: SHA1

On Jan 31, 2005, at 11:25 PM, Jochen Wendebaum wrote:

> 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?

Ideal situation would be this:

Put some common ancestor (the last release code, or after the last
merge) into the trunk. Make two branches, one for each developer,
check out the branches, and overlay the current code from each
developer into their branch, then commit.

Now the merges will have a common ancestor, which should make for
cleaner merges (3 way rather than 2 way), and the change history will
be complete.

- --
- -- Tom Mornini

Version: GnuPG v1.2.4 (Darwin)


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